netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Bolle <pebolle@tiscali.nl>
To: Scott Wood <scottwood@freescale.com>
Cc: igal.liberman@freescale.com, netdev@vger.kernel.org,
	linuxppc-dev@lists.ozlabs.org, madalin.bucur@freescale.com
Subject: Re: [v2,9/9] fsl/fman: Add FMan MAC driver
Date: Fri, 26 Jun 2015 09:01:43 +0200	[thread overview]
Message-ID: <1435302103.28572.54.camel@tiscali.nl> (raw)
In-Reply-To: <1435280369.2977.4.camel@freescale.com>

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 imagine how a patch of a few thousands lines might look like
when replying. (Of course a patch of a few thousands lines is part of
the issue here. As in: no one can really handle that.) 

And if you set certain lines to "preformatted" to undo the wrapping it
inserts ">" in the tabs!

There's more. I'll stop now, as this is drifting too far off topic.

> If you mean the crazy lag when selecting moderate-to-large amounts of 
> 
> text (for snipping), yes.

One of my replies I had to do over a few times because evolution or I
lost track of what was selected. Ie, I thought I had selected hundreds
of lines but something much smaller was deleted. Something like that.
As confusing as it gets, so who knows what actually happened?

Yes, I know, I should ask for a refund.

Thanks,


Paul Bolle

      parent reply	other threads:[~2015-06-26  7:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-24 19:37 [v2,9/9] fsl/fman: Add FMan MAC driver igal.liberman
2015-06-25 23:06 ` Paul Bolle
2015-06-26  0:59   ` Scott Wood
2015-06-26  2:21     ` Michael Ellerman
2015-06-26  2:25       ` Scott Wood
2015-06-29  1:55         ` Michael Ellerman
2015-06-26  7:01     ` Paul Bolle [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1435302103.28572.54.camel@tiscali.nl \
    --to=pebolle@tiscali.nl \
    --cc=igal.liberman@freescale.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=madalin.bucur@freescale.com \
    --cc=netdev@vger.kernel.org \
    --cc=scottwood@freescale.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).