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

From: Michael J Gruber <git@drmicha.warpmail.net>
Date: May 14, 2009, 07:37 UTC
Message-ID: <4A0BCA43.9080408@drmicha.warpmail.net>
In-Reply-To: <20090514063157.GA10411@coredump.intra.peff.net>

Jeff King venit, vidit, dixit 14.05.2009 08:31:

> On Wed, May 13, 2009 at 11:54:20AM +0200, Michael J Gruber wrote:

[snip snip snip]

Show 8 quoted lines

>> My main issue is the fact that we have a config variable (push.default)
>> which causes a different behaviour depending on whether it is unset or
>> set to its default (!) value. That is a completely new UI approach. We
> 
> Well, it depends on how you think of the default. The default could be
> "matched-and-warn", and you are fixing it by setting it to "matched". :)
> 
> -Peff

So, then we have a config variable which you can set to its default value only by /unsetting/ it :)

In fact, I think that approach could be valuable in general, making git more fool-proof for beginners while remaining efficient for the regulars. As a new concept, to be taken up by "deny non-ff pushes", "deny delation pushes", "pull without refspec" etc., I would like that. In order to be useful, beginners should be able to rely on it, i.e.: unless certain config is set, the git-gun should never go off when pointed at users' own feet. Might be a worthy target for 1.7 (pun semi-intended).

Michael