git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Junio C Hamano <gitster@pobox.com>
Cc: Peter Zijlstra <peterz@infradead.org>, git@vger.kernel.org
Subject: Re: [RFC, PATCH] git send-email: Make --no-chain-reply-to the default
Date: Tue, 10 Nov 2009 08:19:27 +0100	[thread overview]
Message-ID: <20091110071927.GB11942@elte.hu> (raw)
In-Reply-To: <7v4op3gd6f.fsf@alter.siamese.dyndns.org>


* Junio C Hamano <gitster@pobox.com> wrote:

> [Footnote]
> 
> *1* To spell it out...  The people who are in the "hate chain-reply-to 
> very much" camp would have already done their own configuration to get 
> the behaviour they want by now, so changing the default would not help 
> them much, while potentially hurting "love chain-reply-to" people who 
> have been content because they got what they wanted without setting 
> any configuration.

Stupid question: i researched the Git mailing list archive (and read the 
link you provided) and found no arguments (at all) in favor of the 
nested chaining. Are you aware of any?

And i dont 'hate' it - i am just the one suffering from it as a 
maintainer. _I_ can certainly fix my scripts as you suggest above, but 
that is not my problem: my problem are the many people sending 
first-time Git based patch series to me (and there's quite a few of 
them) always, in every single case, get it wrong.

The ones not using Git (using Quilt for example) and sending me series 
get it right in pretty much every case.

So i can see it when developers start using Git to submit patches - in 
each and every case - the discussion threading is all messed up ;-)

These people dont 'do their own configuration' - they are mostly newbies 
or developrs new to Git workflows. And the first reaction they get from 
their upstream maintainer counterpart is some grumbling about the 
threading. Not good, me thinks ;-)

	Ingo

  reply	other threads:[~2009-11-10  7:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1257786206-9208-1-git-send-email-mitake@dcl.info.waseda.ac.jp>
     [not found] ` <1257789555.4108.348.camel@laptop>
2009-11-10  4:08   ` [RFC, PATCH] git send-email: Make --no-chain-reply-to the default Ingo Molnar
2009-11-10  5:12     ` Jay Soffian
2009-11-10  5:22       ` Ingo Molnar
2009-11-10  6:05         ` Junio C Hamano
2009-11-10  5:29     ` Junio C Hamano
2009-11-10  7:19       ` Ingo Molnar [this message]
2009-11-10 18:29         ` Ingo Molnar
2009-11-10  7:32     ` Peter Zijlstra
2009-11-10 19:46       ` Michael Witten
2009-11-10 19:58         ` Peter Zijlstra

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=20091110071927.GB11942@elte.hu \
    --to=mingo@elte.hu \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peterz@infradead.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;
as well as URLs for NNTP newsgroup(s).