On Thu, 2015-06-25 at 21:25 -0500, Scott Wood wrote:
On Fri, 2015-06-26 at 12:21 +1000, Michael Ellerman wrote:
On Thu, 2015-06-25 at 19:59 -0500, Scott Wood wrote:
On Fri, 2015-06-26 at 01:06 +0200, Paul Bolle wrote:
(Evolution 3.16 is basically unbearable for replying to patches.
On Thu, 2015-06-25 at 19:59 -0500, Scott Wood wrote:
On Fri, 2015-06-26 at 01:06 +0200, Paul Bolle wrote:
(Evolution 3.16 is basically unbearable for replying to patches.
Anyone
else running into this?)
You replied with Evolution v3.16, didn't you? Look how it wrapped that
line. Now
(Evolution 3.16 is basically unbearable for replying to patches. Anyone
else running into this?)
On Wed, 2015-06-24 at 22:37 +0300, igal.liber...@freescale.com wrote:
--- /dev/null
+++ b/drivers/net/ethernet/freescale/fman/mac/mac-api.c
+int set_mac_active_pause(struct mac_device *mac_dev,
On Thu, 2015-06-25 at 19:59 -0500, Scott Wood wrote:
On Fri, 2015-06-26 at 01:06 +0200, Paul Bolle wrote:
(Evolution 3.16 is basically unbearable for replying to patches.
Anyone
else running into this?)
If you mean the crazy lag when selecting moderate-to-large amounts of
text (for
On Fri, 2015-06-26 at 12:21 +1000, Michael Ellerman wrote:
On Thu, 2015-06-25 at 19:59 -0500, Scott Wood wrote:
On Fri, 2015-06-26 at 01:06 +0200, Paul Bolle wrote:
(Evolution 3.16 is basically unbearable for replying to patches.
Anyone
else running into this?)
If you mean the
On Fri, 2015-06-26 at 01:06 +0200, Paul Bolle wrote:
(Evolution 3.16 is basically unbearable for replying to patches.
Anyone
else running into this?)
If you mean the crazy lag when selecting moderate-to-large amounts of
text (for snipping), yes.
-Scott
