From: Junio C Hamano <junkio@cox.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] We do not like "HEAD" as a new branch name
Date: Thu, 15 Dec 2005 11:34:31 -0800 [thread overview]
Message-ID: <7vacf2p320.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: Pine.LNX.4.63.0512151244230.22400@wbgn013.biozentrum.uni-wuerzburg.de
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> + /* do not allow "HEAD" as ref name */
> + if (ch == 'H' && (!strcmp(cp, "EAD") ||
> + !strncmp(cp, "EAD/", 4)))
Why forbid HEAD in the middle, like "refs/heads/HEAD/frotz"?
Confusion avoidance?
We might want to forbid anything that matches /^.*_?HEAD$/ to catch
ORIG_HEAD for example, though.
next prev parent reply other threads:[~2005-12-15 19:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-15 11:46 [PATCH] We do not like "HEAD" as a new branch name Johannes Schindelin
2005-12-15 16:27 ` H. Peter Anvin
2005-12-15 16:40 ` Johannes Schindelin
2005-12-15 17:00 ` Alex Riesen
2005-12-15 19:34 ` Junio C Hamano [this message]
2005-12-15 22:41 ` Johannes Schindelin
2005-12-15 23:38 ` Junio C Hamano
2005-12-16 1:40 ` Johannes Schindelin
2005-12-16 6:34 ` Junio C Hamano
2005-12-16 11:32 ` 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=7vacf2p320.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
/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).