From: Junio C Hamano <gitster@pobox.com>
Date: Wed, 11 Feb 2009 01:04:11 GMT
Subject: Re: [PATCH] Switch receive.denyCurrentBranch to "refuse"
Message-ID: <7vskmliy2c.fsf@gitster.siamese.dyndns.org>
In-Reply-To: <20090211001138.GU21473@genesis.frugalware.org>

Miklos Vajna <vmiklos@frugalware.org> writes:

> [ 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"?

If you have to ask, you do not know what you're doing ;-)