From: Junio C Hamano <gitster@pobox.com>
To: Matt McCutchen <matt@mattmccutchen.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git checkout: don't warn about unborn branch if -f is already passed
Date: Wed, 26 Nov 2008 11:46:42 -0800 [thread overview]
Message-ID: <7vr64yfexp.fsf@gitster.siamese.dyndns.org> (raw)
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?
next prev parent reply other threads:[~2008-11-26 19:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-24 6:55 [PATCH] git checkout: don't warn about unborn branch if -f is already passed Matt McCutchen
2008-11-26 19:46 ` Junio C Hamano [this message]
2008-12-01 16:47 ` Matt McCutchen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vr64yfexp.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=matt@mattmccutchen.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.