From: Miklos Vajna <vmiklos@frugalware.org>
Date: Wed, 11 Feb 2009 00:11:38 GMT
Subject: Re: [PATCH] Switch receive.denyCurrentBranch to "refuse"
Message-ID: <20090211001138.GU21473@genesis.frugalware.org>
In-Reply-To: <alpine.DEB.1.00.0901301426150.3586@pacific.mpi-cbg.de>

[ Sorry for the late reply, I did not read my mail recently. ]

On Fri, Jan 30, 2009 at 02:28:39PM +0100, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> > Shouldn't this be
> > 
> > git config receive.denyCurrentBranch ignore
> > 
> > instead of "true"?
> 
> Right.
> 
> However, as Junio pointed out, we do not want to give this resolution in 
> the error message.  I am now leaning more to something like
> 
> 	refusing to update checked out branch '%s' in non-bare repository
> 
> Hmm?
> 
> Old-timers will know "oh, what the hell, I did not mark my repository as 
> bare!", and new-timers will no longer be confused.

So in an "I know what I'm doing" mode, is "git config core.bare true" in
a non-bare repo considered as a better workaround than using "git config
receive.denyCurrentBranch ignore"?