From: Adrian Bunk <bunk@kernel.org>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: WANG Cong <xiyou.wangcong@gmail.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 17:43:28 +0200 [thread overview]
Message-ID: <20070912154328.GZ3563@stusta.de> (raw)
In-Reply-To: <46E7FF85.1090806@oracle.com>
On Wed, Sep 12, 2007 at 08:02:29AM -0700, Randy Dunlap wrote:
> Adrian Bunk wrote:
>> On Wed, Sep 12, 2007 at 01:24:13PM +0800, WANG Cong wrote:
>>> 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"`.
>> This makes sense, but it's not really a mutt specific issue and problems
>> because mutt prefers iso-8859-1 over UTF-8 by default are
>> quite rare.
>>> 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.
>>> ...
>> Whether or not people want to get personal copies of answers to mailing
>> list posts is a religious issue being second only to the vi<->emacs
>> wars...
>> But as far as I understand it, this documentation is intended to help
>> people to get sending patches right (no line wrap etc.), not as a generic
>> documentation for mail clients.
>
> Definitely.
> and to reduce the amount of repetition that we have to do.
>
> I'll add a bit about it not being complete s/w package config info.
One point from this email that might be appropriate for the
"General Preferences" section of your document would be to suggest
configuring the MUA to send text encoded as UTF-8, something like:
The kernel source code is encoded in UTF-8, and if you configure your
email client to send emails UTF-8 encoded you avoid some possible
charset problems.
> thanks,
> ~Randy
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2007-09-12 15:43 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
2007-09-12 5:55 ` Adrian Bunk
2007-09-12 15:02 ` Randy Dunlap
2007-09-12 15:43 ` Adrian Bunk [this message]
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=20070912154328.GZ3563@stusta.de \
--to=bunk@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=xiyou.wangcong@gmail.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