From: Joel Becker <Joel.Becker@oracle.com>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Junio C Hamano <junio@pobox.com>,
Lennart Sorensen <lsorense@csclub.uwaterloo.ca>,
Ingo Oeser <ioe-lkml@rameria.de>,
Peter Zijlstra <peterz@infradead.org>,
L-K <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: git-send-email
Date: Mon, 16 Feb 2009 12:58:18 -0800 [thread overview]
Message-ID: <20090216205818.GA12345@ca-server1.us.oracle.com> (raw)
In-Reply-To: <49984ED4.4000306@s5r6.in-berlin.de>
On Sun, Feb 15, 2009 at 06:20:20PM +0100, Stefan Richter wrote:
> Junio C Hamano wrote:
> > Just like the kernel folks take regressions seriously to the point to say
> > breaking one person's working setup is worse than fixing a known bug that
> > affects many more people,
>
> BTW, 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.
Actually, the big trouble is when you log into a machine that
doesn't have your config and don't realize it. I have the configuration
option set, and I still put --no-chain-reply-to on every command line,
because I've been bitten before.
The problem with the default of --chain-reply-to is that many
folks consider the resulting email chain rude and stupid. So the
consequence of not putting it on every command line is occasionally
looking like an idiot.
Joel
--
f/8 and be there.
Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker@oracle.com
Phone: (650) 506-8127
next prev parent reply other threads:[~2009-02-16 21:01 UTC|newest]
Thread overview: 20+ 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 ` git-send-email Stefan Richter
2009-02-16 20:58 ` Joel Becker [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2007-02-22 21:13 git-send-email Uwe Kleine-König
2007-02-22 21:38 ` git-send-email Junio C Hamano
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=20090216205818.GA12345@ca-server1.us.oracle.com \
--to=joel.becker@oracle.com \
--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=stefanr@s5r6.in-berlin.de \
--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 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.