From: Michael Ellerman <mpe@ellerman.id.au>
To: Scott Wood <scottwood@freescale.com>
Cc: igal.liberman@freescale.com, Paul Bolle <pebolle@tiscali.nl>,
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: Mon, 29 Jun 2015 11:55:48 +1000 [thread overview]
Message-ID: <1435542948.26549.2.camel@ellerman.id.au> (raw)
In-Reply-To: <1435285530.4306.33.camel@freescale.com>
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.
> > > > Anyone
> > > > else running into this?)
> > >
> > > If you mean the crazy lag when selecting moderate-to-large amounts of
> > > text (for snipping), yes.
> >
> > I recommend the external editor plugin with vim.
>
> I tried the external editor plugin (not with vim) and it failed to bring the
> externally made edits back into the evolution compose window. It then
> started spastically respawning the external editor without my doing anything.
I guess it only works with vim ;)
cheers
_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
next prev parent reply other threads:[~2015-06-29 1:55 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 [this message]
2015-06-26 7:01 ` Paul Bolle
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=1435542948.26549.2.camel@ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=igal.liberman@freescale.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=madalin.bucur@freescale.com \
--cc=netdev@vger.kernel.org \
--cc=pebolle@tiscali.nl \
--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).