Re: git push origin error (1.6.3 new default functionality)

From: Junio C Hamano <gitster@pobox.com>
Date: May 13, 2009, 18:37 UTC
Message-ID: <7vprec4znj.fsf@alter.siamese.dyndns.org>
In-Reply-To: <4A09594F.4040603@drmicha.warpmail.net>

Michael J Gruber <git@drmicha.warpmail.net> writes:

Show 7 quoted lines

> Seriously, we had that discussion when the feature (change of default
> behaviour) and warning were introduced, so it's too late for a change.
> But it's never too late to do
>
> git config --global push.default matching
>
> and be done with it.

Thanks for saying this concisely, and saving me from repeating this.

> The weird thing is that the default is "matching" already. But it makes
> a difference whether you have set the variable to its default value
> explicitly or not. No man page says so (neither git-push nor
> git-config), and I can't think of other variables with such a behaviour.

It is not weird at all. Although I am still not convinced (and I suspect some old timers are not either), the default could change in the future and by setting it to 'matching', you will protect yourself from such a change. Consider it a vaccination ;-)