From: Jeff King <peff@peff.net>
To: Philip Oakley <philipoakley@iee.email>
Cc: Chris Torek <chris.torek@gmail.com>,
Craig H Maynard <chmaynard@me.com>,
git@vger.kernel.org
Subject: Re: Regarding Git and Branch Naming
Date: Fri, 26 Jun 2020 23:11:11 -0400 [thread overview]
Message-ID: <20200627031111.GB1187031@coredump.intra.peff.net> (raw)
In-Reply-To: <6b9d76e4-68dd-8e57-f96a-318579dea6f3@iee.email>
On Fri, Jun 26, 2020 at 10:33:14PM +0100, Philip Oakley wrote:
> A wild bikeshed question: Is HEAD itself protected as a branch name e.g.
> that HEAD could contain `ref: HEAD` or `ref: refs/heads/HEAD`? (or maybe
> the null oid
The first is not legal; we insist that symrefs start with "refs/". The
second one _is_ legal, but isn't any kind of loop. The HEAD symref is
.git/HEAD, which is distinct from a ref of the same name inside
refs/heads/.
It's confusing, of course, because the lookup rules make it hard to
refer to refs/heads/HEAD. For that reason we do disallow it from the
branch-creation porcelains like git-branch and git-checkout.
-Peff
next prev parent reply other threads:[~2020-06-27 3:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-26 16:18 Regarding Git and Branch Naming Craig H Maynard
2020-06-26 18:33 ` Chris Torek
2020-06-26 20:35 ` Jeff King
2020-06-26 21:07 ` Junio C Hamano
2020-06-27 3:05 ` Jeff King
2020-06-26 21:33 ` Philip Oakley
2020-06-27 3:11 ` Jeff King [this message]
2020-06-26 21:58 ` Elijah Newren
2020-06-27 3:14 ` Jeff King
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200627031111.GB1187031@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=chmaynard@me.com \
--cc=chris.torek@gmail.com \
--cc=git@vger.kernel.org \
--cc=philipoakley@iee.email \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).