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

From: Sam Vilain <sam@vilain.net>
Date: Feb 2, 2009, 07:00 UTC
Message-ID: <1233558035.20131.72.camel@maia.lan>
In-Reply-To: <7vbptlsuyv.fsf@gitster.siamese.dyndns.org>

On Sun, 2009-02-01 at 13:33 -0800, Junio C Hamano wrote:

Show 8 quoted lines

> > 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..
> 
> There is no resitance to any safety feature.  The resistance is to
> something entirely different.

  [...]

> Perhaps you already forgot the fiasco after 1.6.0, which moved tons of
> git-foo scripts out of the users' way.  It resulted in a better layout in
> the end, but we knew it would break people's working setup from the
> beginning.

  [...]

Yeah sure but the changes are a bit different aren't they. One affected all users who used the previously documented way to access subcommands (and the names that the man pages all still retain). The other affects a small number of users who are doing something which is labeled in many places as a bad thing to want to do.

That being said, I think I like the copy and design of the patch you just posted. If the path of caution is to be followed for this, then the way you propose seems a good way to do it.

Sam