git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] git checkout: don't warn about unborn branch if -f is already passed

From
Junio C Hamano <gitster@pobox.com>
Date
Nov 26, 2008, 19:46 UTC
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?
Previous: Matt McCutchenNext: Matt McCutchen
Message 2 of 3 in “git checkout: don't warn about unborn branch if -f is already passed”
  1. git checkout: don't warn about unborn branch if -f is already passedMatt McCutchen, Nov 24, 2008
  2. Junio C HamanoNov 26, 2008
  3. Matt McCutchenDec 1, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.