Sverre Rabbelier <srabbelier@xxxxxxxxx> writes: > On Mon, Feb 14, 2011 at 19:53, Jay Soffian <jaysoffian@xxxxxxxxx> wrote: >> Âpush.default is unset; its implicit value is changing in 1.8.0. To squelch >> Âthis message, set push.default. See push.default in 'git help config'. > > This is worse than what Junio suggested because it does not tell you > what to set it to. But the weatherbaloon patch from me was equally bad in another sense. I was only showing where the change should go, and not what the precise wording should be. The message triggers not just for people who _do_ use and want to keep using matching semantics (iow, old timers), for whom the weatherbaloon wording is adequate, but also for people who are new and do not have anything configured, majority of which are _suspected_ to be better off using "current" setting (if we don't suspect that, we won't be talking about possibly switching the default in the future). So I would imagine the actual wording should at least explain that there are two plausible choices, and people who want to get used to the upcoming default earlier would want to set it to "current", while others who want to keep the current default would want to set it to "matching", to avoid surprises. -- 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