From: Petr Baudis <pasky@suse.cz>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Documentation: Define symref and update HEAD description
Date: Sat, 18 Nov 2006 22:31:54 +0100 [thread overview]
Message-ID: <20061118213153.GR7201@pasky.or.cz> (raw)
In-Reply-To: <7v64dccyx2.fsf@assigned-by-dhcp.cox.net>
On Sat, Nov 18, 2006 at 08:55:37PM CET, Junio C Hamano wrote:
> Petr Baudis <pasky@suse.cz> writes:
>
> > HEAD was still described as a symlink instead of a symref.
> >...
> > HEAD::
> > + A symref (see glossary) to the `refs/heads/` namespace
> > + describing the currently active branch. It does not mean
> > + much if the repository is not associated with any working tree
> > (i.e. a 'bare' repository), but a valid git repository
> > + *must* have the HEAD file; some porcelains may use it to
> > + guess the designated "default" branch of the repository
> > + (usually 'master'). It is legal if the named branch
> > + 'name' does not (yet) exist. In some legacy setups, it is
> > + a symbolic link instead of a symref, but this has been
> > + deprecated long ago.
>
> We fully support dealing with repositories with symlinked HEAD,
> and will continue to do so; I do not think we ever talked about
> deprecating it. Public "distribution point" repositories that
> have been established long ago that do not have reason to switch
> HEAD to point at different branch still have symlinked HEAD and
> they should continue to work.
>
> What we _don't_ do these days is to set up new repositories with
> symlinked HEAD, but that does not have anything to do with
> deprecating symlinked HEAD.
That's true, perhaps "obsoleted" is a better word.
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
The meaning of Stonehenge in Traflamadorian, when viewed from above, is:
"Replacement part being rushed with all possible speed."
prev parent reply other threads:[~2006-11-18 21:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-18 19:44 [PATCH] Documentation: Define symref and update HEAD description Petr Baudis
2006-11-18 19:55 ` Junio C Hamano
2006-11-18 21:31 ` Petr Baudis [this message]
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=20061118213153.GR7201@pasky.or.cz \
--to=pasky@suse.cz \
--cc=git@vger.kernel.org \
--cc=junkio@cox.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 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).