From: WANG Cong <xiyou.wangcong@gmail.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Lee Revell <rlrevell@joe-job.com>,
Randy Dunlap <randy.dunlap@oracle.com>,
lkml <linux-kernel@vger.kernel.org>,
akpm <akpm@linux-foundation.org>, jgarzik <jgarzik@pobox.com>
Subject: Re: [PATCH/RFC] doc: about email clients for Linux kernel patches
Date: Wed, 12 Sep 2007 13:07:51 +0800 [thread overview]
Message-ID: <20070912050751.GG2579@hacking> (raw)
In-Reply-To: <1189536734.5739.2.camel@lappy>
On Tue, Sep 11, 2007 at 08:52:14PM +0200, Peter Zijlstra wrote:
>
>On Tue, 2007-09-11 at 14:38 -0400, Lee Revell wrote:
>> On 9/11/07, Peter Zijlstra <peterz@infradead.org> wrote:
>> > On Tue, 2007-09-11 at 10:16 -0700, Randy Dunlap wrote:
>> >
>> > > +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> > > +Evolutions (GUI)
>> >
>> > I take it you mean: Evolution
>> >
>> > > +Some people seem to use this successfully for patches.
>> > > +
>> > > +What config options are needed?
>> >
>> > When composing mail select: Preformat
>> > from Format->Heading->Preformatted (Ctrl-7)
>> > or the toolbar
>> >
>> > Then use:
>> > Insert->Text File... (Alt-n x)
>> >
>> > to insert the patch.
>>
>> You can also diff -Nru old.c new.c | xclip, select Preformat, then
>> paste with the middle button.
>
>Ah, I shall try:
>
> cat `quilt top` | xclip
>
>next time I have a single patch to send.
>
Oh, great! Thank you for this hint.
--
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2007-09-12 5:11 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-11 17:16 [PATCH/RFC] doc: about email clients for Linux kernel patches Randy Dunlap
2007-09-11 17:36 ` Peter Zijlstra
2007-09-11 18:38 ` Lee Revell
2007-09-11 18:52 ` Peter Zijlstra
2007-09-12 5:07 ` WANG Cong [this message]
2007-09-11 22:05 ` Sami Farin
2007-09-12 3:40 ` Randy Dunlap
2007-09-11 18:03 ` Nicolas Pitre
2007-09-11 18:17 ` Adrian Bunk
2007-09-11 18:31 ` Nicolas Pitre
2007-09-11 18:46 ` Adrian Bunk
2007-09-11 19:09 ` Jan Engelhardt
2007-09-11 19:08 ` Jan Engelhardt
2007-09-11 18:29 ` Adrian Bunk
2007-09-12 5:24 ` WANG Cong
2007-09-12 5:55 ` Adrian Bunk
2007-09-12 15:02 ` Randy Dunlap
2007-09-12 15:43 ` Adrian Bunk
2007-09-11 19:37 ` Chris Friesen
2007-09-11 19:42 ` Martin Bligh
2007-09-11 19:55 ` Jeff Garzik
2007-09-12 3:26 ` Chris Friesen
2007-09-12 18:08 ` Jan Engelhardt
2007-09-12 18:17 ` Chris Friesen
2007-09-12 22:35 ` Stefan Richter
2007-09-12 19:16 ` Rik van Riel
2007-09-12 19:53 ` Peter Zijlstra
2007-09-12 23:09 ` Adrian Bunk
2007-09-11 19:54 ` Stefan Richter
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=20070912050751.GG2579@hacking \
--to=xiyou.wangcong@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=randy.dunlap@oracle.com \
--cc=rlrevell@joe-job.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