From: "Kevin P. Fleming" <kpfleming@digium.com>
To: Tomas Carnecky <tom@dbservice.com>
Cc: Emeric Fermas <emeric.fermas@gmail.com>,
Kevin Ballard <kevin@sb.org>,
git@vger.kernel.org, Vicent Marti <tanoku@gmail.com>,
libgit2@librelist.com
Subject: Re: What's the definition of a valid Git symbolic reference?
Date: Sat, 19 Feb 2011 07:10:50 -0600 [thread overview]
Message-ID: <4D5FC15A.30309@digium.com> (raw)
In-Reply-To: <4D5A0901.7080202@dbservice.com>
On 02/14/2011 11:02 PM, Tomas Carnecky wrote:
> On 2/15/11 4:49 AM, Emeric Fermas wrote:
>> Another possibility would be that only git internal symbolic
>> references are allowed to live under the ".git" dir (HEAD, FETCH_HEAD,
>> ...) and that user defined symrefs should live under refs/. In this
>
> All refs should live under refs/ (except the special ones like HEAD
> etc). It's usually a mistake if someone manages to create one outside of
> refs/. The plumbing commands allow you to do that, but users usually
> shouldn't use those.
Being able to manually point HEAD at a ref is actually useful; when I've
created repos that start out with a 'vendor branch', I want to do the
initial import into a branch called 'upstream', not 'master'. Using 'git
symbolic-ref HEAD refs/heads/upstream' in a brand-new repo allows that
to happen, and works quite well.
Please don't take it away :-)
--
Kevin P. Fleming
Digium, Inc. | Director of Software Technologies
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
skype: kpfleming | jabber: kfleming@digium.com
Check us out at www.digium.com & www.asterisk.org
next prev parent reply other threads:[~2011-02-19 13:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-14 20:58 What's the definition of a valid Git symbolic reference? Emeric Fermas
2011-02-15 3:19 ` Kevin Ballard
2011-02-15 3:49 ` Emeric Fermas
2011-02-15 5:02 ` Tomas Carnecky
2011-02-19 13:10 ` Kevin P. Fleming [this message]
2011-02-15 6:22 ` Junio C Hamano
2011-02-15 6:32 ` Emeric Fermas
2011-02-15 7:09 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D5FC15A.30309@digium.com \
--to=kpfleming@digium.com \
--cc=emeric.fermas@gmail.com \
--cc=git@vger.kernel.org \
--cc=kevin@sb.org \
--cc=libgit2@librelist.com \
--cc=tanoku@gmail.com \
--cc=tom@dbservice.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).