Re: [PATCH] Switch receive.denyCurrentBranch to "refuse"

From: Sam Vilain <sam@vilain.net>
Date: Feb 1, 2009, 03:37 UTC
Message-ID: <1233459475.17688.128.camel@maia.lan>
In-Reply-To: <7v63juzz9m.fsf@gitster.siamese.dyndns.org>

On Sat, 2009-01-31 at 18:06 -0800, Junio C Hamano wrote:

Show 15 quoted lines

> Nanako Shiraishi <nanako3@lavabit.com> writes:
> 
> > I assume that everybody, including the maintainer who is too heavyweight
> > and has too much inertia to accept too sudden a change of the course,
> > wants to eventually make the default to deny pushing to the current
> > branch. But I think such a change should come at 1.7.0 release at the
> > earliest, and a constructive thing to do is to put in a patch to 1.6.2
> > that helps the users with the eventual transition.
> 
> I am not opposed to eventually change the default to refuse at some point,
> but I have to say that now would not be the best time to do so.  Jeff's
> 986e823 (receive-pack: detect push to current branch of non-bare repo,
> 2008-11-08) that is v1.6.1-rc1~59^2 was the one we started warning about
> this, and we only had one major release since then, and I'd love to see a
> solid rc or even the final release by mid February.

Personally I think it's worth fast tracking, because I think very few people are actually using push to a checked out branch whereas many people are confused by the behaviour. I just can't understand the resistance to this safety feature. People who encounter the bug can just change the setting and move on... it seems like an argument based on "principles", usually a sign that one has run out of actual arguments..

> By the way, I do not appreciate other people who I have never met
> speculate about my body mass very much.  I am on the skinner end of the
> spectrum, if you need to know.

lol.  It was a metaphorical use of the term from my reading ;-)

Sam.