* Junio C Hamano <gitster@xxxxxxxxx> 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 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html