From: Junio C Hamano <gitster@pobox.com>
Date: Wed, 26 Nov 2008 19:46:42 GMT
Subject: Re: [PATCH] git checkout: don't warn about unborn branch if -f is already passed
Message-ID: <7vr64yfexp.fsf@gitster.siamese.dyndns.org>
In-Reply-To: <1227509722.32583.0.camel@mattlaptop2.local>

Matt McCutchen <matt@mattmccutchen.net> writes:

> I think it's unnecessary to warn that the checkout has been forced due to an
> unborn current branch if -f has been explicitly passed.  For one project, I am
> using git-new-workdir to create workdirs from a bare repository whose HEAD is
> set to an unborn branch, and this warning started to irritate me.

I doubt anybody minds this particular change per-se, but I wonder what the
justification of keeping a dangling HEAD in a bare repository is.

After all, the primary intended purpose of a bare repository is to serve
as a distribution point (i.e. something you can clone from), and I think a
dangling HEAD interferes with the usual operation of clone (although I've
never tested this).

Care to explain why?