mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Junio C Hamano <junio@pobox.com>,
	Lennart Sorensen <lsorense@csclub.uwaterloo.ca>,
	Ingo Oeser <ioe-lkml@rameria.de>,
	L-K <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: git-send-email
Date: Sun, 15 Feb 2009 20:25:37 +0100	[thread overview]
Message-ID: <49986C31.90800@s5r6.in-berlin.de> (raw)
In-Reply-To: <1234722605.4713.192.camel@laptop>

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/

  reply	other threads:[~2009-02-15 19:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-12 15:15 git-send-email Peter Zijlstra
2009-02-12 17:25 ` git-send-email Ingo Oeser
2009-02-12 17:27   ` git-send-email Peter Zijlstra
2009-02-12 19:21   ` git-send-email Lennart Sorensen
2009-02-12 22:17     ` git-send-email Peter Zijlstra
2009-02-13  9:34       ` git-send-email Ingo Oeser
2009-02-13 16:39         ` git-send-email Lennart Sorensen
2009-02-13 22:25           ` git-send-email Junio C Hamano
2009-02-15 17:20             ` git-send-email Stefan Richter
2009-02-15 18:30               ` git-send-email Peter Zijlstra
2009-02-15 19:25                 ` Stefan Richter [this message]
2009-02-16 20:58               ` git-send-email Joel Becker
2009-02-13  2:16     ` git-send-email Junio C Hamano
2009-02-13  9:22       ` git-send-email Peter Zijlstra
2009-02-13  9:27         ` git-send-email Willy Tarreau
2009-02-13 18:13       ` git-send-email H. Peter Anvin
2009-02-13 18:59         ` git-send-email Cyrill Gorcunov
2009-02-16 23:51 ` git-send-email Jeremy Fitzhardinge

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=49986C31.90800@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=ioe-lkml@rameria.de \
    --cc=junio@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lsorense@csclub.uwaterloo.ca \
    --cc=peterz@infradead.org \
    --cc=torvalds@linux-foundation.org \
    /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

all inboxes | Powered by JetHome®