All of lore.kernel.org
 help / color / mirror / Atom feed
From: WANG Cong <xiyou.wangcong@gmail.com>
To: Adrian Bunk <bunk@kernel.org>
Cc: 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:24:13 +0800	[thread overview]
Message-ID: <20070912052413.GH2579@hacking> (raw)
In-Reply-To: <20070911182926.GQ3563@stusta.de>

On Tue, Sep 11, 2007 at 08:29:26PM +0200, Adrian Bunk wrote:
>On Tue, Sep 11, 2007 at 10:16:44AM -0700, Randy Dunlap wrote:
>>...
>> +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> +Mutt (TUI)
>> +
>> +Plenty of Linux developers use mutt, so it must work pretty well.
>> +
>> +Are there any special config options that are needed??
>>...
>
>It should work with default settings.


I can't agree with this.

It took me lots of time to configure mutt to work well for me in the first
time. Just default settings are far _not_ enough, especially for us
non-english-speakers. One common setting is the encoding, of course, lkml
prefers UTF-8, so I must set my mutt with `set send_charset="us-ascii:utf-8"`.

Manuals of mutt told me to add "subscribe linux-kernel@vger.kernel.org" if I
subscribed lkml, but in fact, we'd better _not_ add this, or it will drop
myself from cc list.

Or other things like these.

>
>mutt doesn't come with an editor, so whatever editor you use should be 
>used in a way that there are no automatic linebreaks. Most editors have 
>an "insert file" option that inserts the contents of a file unaltered.
>

Yes, you can `set editor="vi"` or other editors you prefer.


Regards.

-- 
"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."


  reply	other threads:[~2007-09-12  5:27 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
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 [this message]
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=20070912052413.GH2579@hacking \
    --to=xiyou.wangcong@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=bunk@kernel.org \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.