From: Junio C Hamano <junkio@cox.net>
To: Andreas Ericsson <ae@op5.se>
Cc: linux@horizon.com, git@vger.kernel.org
Subject: Re: Why can't git-rebase back up?
Date: Fri, 17 Feb 2006 23:39:26 -0800 [thread overview]
Message-ID: <7vhd6xru8h.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: 43F5FA10.5020605@op5.se
Andreas Ericsson <ae@op5.se> writes:
> The order of precedence works as such:
> .git/<anchor-name>
> .git/refs/<anchor-name>
> .git/refs/tags/<tag-name>
> .git/refs/heads/<branch-name>
> sha1, with git magic to allow abbreviations
>
> This is why you can't sanely have a branch named HEAD.
Actually, you should be able to sanely have a branch named HEAD.
When git barebone Porcelain tools _expect_ branch name from the
user (not just a random committish), they _ought_ to prefix
"refs/heads" in front of it, exactly in order to help
disambiguate things.
Otherwise you have spotted a bug, so please send in a fix.
It is however a different story if you can keep your sanity if
you created a branch called HEAD. You have to remember to
explicitly say refs/heads/HEAD, where a command wants any
committish or treeish.
next prev parent reply other threads:[~2006-02-18 7:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-17 13:59 Why can't git-rebase back up? linux
2006-02-17 14:36 ` Andreas Ericsson
2006-02-17 15:34 ` linux
2006-02-17 16:30 ` Andreas Ericsson
2006-02-18 7:39 ` Junio C Hamano [this message]
2006-02-18 7:39 ` Junio C Hamano
2006-02-18 8:56 ` linux
2006-02-18 9:15 ` Junio C Hamano
2006-02-18 13:00 ` linux
2006-02-18 14:53 ` Johannes Schindelin
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=7vhd6xru8h.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=linux@horizon.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).