From: Cyrill Gorcunov <gorcunov@gmail.com>
To: "H. Peter Anvin" <hpa@zytor.com>
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: Fri, 13 Feb 2009 21:59:16 +0300 [thread overview]
Message-ID: <20090213185916.GA22651@localhost> (raw)
In-Reply-To: <4995B83C.6000108@zytor.com>
[H. Peter Anvin - Fri, Feb 13, 2009 at 10:13:16AM -0800]
| Junio C Hamano wrote:
| >
| > I personally prefer the former, but as you hopefully all found out by now,
| > the choice between these two is just the matter of personal taste, and
| > there is no clear majority.
| >
|
| Quite on the contrary. I think there is a clear majority in favor of
| --no-chain-reply-to. Let me add my voice to that chorus, too.
|
| -hpa
|
| --
| H. Peter Anvin, Intel Open Source Technology Center
| I work for Intel. I don't speak on their behalf.
|
If that somehow matter -- I'm _for_ --no-chain-reply-to
by default too. It happens several times with me that
I missed this option even having in mind --no-chain-reply-to
behaviour expected.
On the other hand I think --no-chain-reply-to has much
sense if pathes being sent are not numbered in title.
But on LKML I can't remember even one mail-thread which was
not numbered :)
- Cyrill -
next prev parent reply other threads:[~2009-02-13 18:59 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 ` 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 ` Cyrill Gorcunov [this message]
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=20090213185916.GA22651@localhost \
--to=gorcunov@gmail.com \
--cc=hpa@zytor.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=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.