git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [RFC, PATCH] git send-email: Make --no-chain-reply-to the default

From
IMIngo Molnar <mingo@elte.hu>
Date
Nov 10, 2009, 18:29 UTC
Message-ID
<20091110182942.GA15677@elte.hu>
In-Reply-To
<20091110071927.GB11942@elte.hu>
* Ingo Molnar <mingo@elte.hu> wrote:
Show 14 quoted lines
> * 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?

Btw., dont get me wrong - i'm perfectly happy with the fix in 1.7.0. You are also right that behavioral changes dont belong into stable releases.

( I'm just seeing this problem through the biased eyes of someone who is
  affected by it, so i naturally want to have the benefit of the change
  ASAP - without fully perceiving the risks of the change.)
Thanks,
	Ingo
Previous: Ingo MolnarNext: Peter Zijlstra
Message 7 of 10 in “git send-email: Make --no-chain-reply-to the default”
  1. git send-email: Make --no-chain-reply-to the defaultIngo Molnar, Nov 10, 2009
  2. Jay SoffianNov 10, 2009
  3. Ingo MolnarNov 10, 2009
  4. Junio C HamanoNov 10, 2009
  5. Junio C HamanoNov 10, 2009
  6. Ingo MolnarNov 10, 2009
  7. Ingo MolnarNov 10, 2009
  8. Peter ZijlstraNov 10, 2009
  9. Michael WittenNov 10, 2009
  10. Peter ZijlstraNov 10, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.