[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090216205818.GA12345@ca-server1.us.oracle.com>
Date: Mon, 16 Feb 2009 12:58:18 -0800
From: Joel Becker <Joel.Becker@...cle.com>
To: Stefan Richter <stefanr@...6.in-berlin.de>
Cc: Junio C Hamano <junio@...ox.com>,
Lennart Sorensen <lsorense@...lub.uwaterloo.ca>,
Ingo Oeser <ioe-lkml@...eria.de>,
Peter Zijlstra <peterz@...radead.org>,
L-K <linux-kernel@...r.kernel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: git-send-email
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@...cle.com
Phone: (650) 506-8127
--
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