From: Dmitry Potapov <dpotapov@gmail.com>
Date: Thu, 08 Mar 2012 17:49:39 GMT
Subject: Re: git push default behaviour?
Message-ID: <CAHkcotiOGaOdDvibpoiEgys3PnSPfSw0mT3DeEOix+FuboULiA@mail.gmail.com>
In-Reply-To: <vpq62efjeqd.fsf@bauges.imag.fr>

On Thu, Mar 8, 2012 at 7:26 PM, Matthieu Moy
<Matthieu.Moy@grenoble-inp.fr> wrote:
>
> 'push.default = matching' is never a good idea if you use shared
> repository actually. It makes sense for people like Junio pushing a
> local repository to a public one, which is read-only for the rest of the
> world. But my experience is that people using such workflow are advanced
> users, and would know how to configure Git, so it wouldn't really harm
> them to change the default.

There are more people that you think who rely on the current behavior
of git push. For instance, pushing changes between different computers
for testing purposes before publishing them. When you silently change
the default value of push, you silently break their workflow. It is not
difficult to add 'push.default = matching' but you need to know that the
default value has changed, so you have to add this line to preserve the
old behavior.

Dmitry