[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <49986C31.90800@s5r6.in-berlin.de>
Date: Sun, 15 Feb 2009 20:25:37 +0100
From: Stefan Richter <stefanr@...6.in-berlin.de>
To: Peter Zijlstra <peterz@...radead.org>
CC: Junio C Hamano <junio@...ox.com>,
Lennart Sorensen <lsorense@...lub.uwaterloo.ca>,
Ingo Oeser <ioe-lkml@...eria.de>,
L-K <linux-kernel@...r.kernel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: git-send-email
Peter Zijlstra wrote:
> On Sun, 2009-02-15 at 18:20 +0100, Stefan Richter wrote:
>> from the manual:
>>
>> --chain-reply-to, --no-chain-reply-to
>> [...] Default is the value of the sendemail.chainreplyto
>> configuration value; if that is unspecified, default to
>> --chain-reply-to.
>>
>> Everybody who isn't afraid of configuration files can implement his
>> preferred default easily.
>
> Yep, trouble is with all those folks who
>
> 1) don't know about the option
> 2) aren't educated to know its a good idea to use it
>
> So by changing the default we're better off all around.
There will always be trouble with these folks. ;-)
Two more thoughts: Since git-send-email puts sequence information into
the Subject header, additional sequence info in the References header is
redundant. It is sufficient that the References or In-Reply-To header
carries information about which mail thread a posting belongs to.
On the other hand, --no-chain-reply-to makes less sense if the thread
starts with a 1/n posting instead of an introductory 0/n one.
(What if git-send-email could optionally generate a 0/n posting with
shortlog and combined diffstat as default content?)
--
Stefan Richter
-=====-==--= --=- -====
http://arcgraph.de/sr/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists