From: Junio C Hamano <gitster@pobox.com>
To: Michael Haggerty <mhagger@alum.mit.edu>
Cc: Shawn Pearce <spearce@spearce.org>, git <git@vger.kernel.org>,
David Turner <dturner@twopensource.com>,
Jeff King <peff@peff.net>, Martin Fick <mfick@codeaurora.org>
Subject: Re: RefTree: Alternate ref backend
Date: Wed, 23 Dec 2015 17:33:00 -0800 [thread overview]
Message-ID: <xmqqsi2sbpgz.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <567A2A44.3050003@alum.mit.edu> (Michael Haggerty's message of "Wed, 23 Dec 2015 05:59:48 +0100")
Michael Haggerty <mhagger@alum.mit.edu> writes:
> You are answering "What is 'refs/' good for in the pathnames of files
> that store loose references?" I was asking "What is 'refs/' good for in
> the logical names of references?"
>
> It would have been totally possible to make the full name of a branch
> be, for example, "heads/master" and nevertheless store its loose
> reference in "$GIT_DIR/refs/heads/master". The obvious place to store
> HEAD in such a scheme would have been "$GIT_DIR/refs/HEAD" while still
> calling it "HEAD". This could have avoided the problem that we now have
> with pseudo-references like FETCH_HEAD being stored directly in $GIT_DIR.
I see; OK.
next prev parent reply other threads:[~2015-12-24 1:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 21:02 RefTree: Alternate ref backend Shawn Pearce
2015-12-17 21:57 ` Junio C Hamano
2015-12-17 22:15 ` Shawn Pearce
2015-12-17 22:10 ` Jeff King
2015-12-17 22:28 ` Shawn Pearce
2015-12-18 1:36 ` Mike Hommey
2015-12-22 15:41 ` Michael Haggerty
2015-12-22 16:11 ` Shawn Pearce
2015-12-22 17:04 ` Dave Borowitz
2015-12-22 17:17 ` Michael Haggerty
2015-12-22 18:50 ` Shawn Pearce
2015-12-22 19:09 ` Junio C Hamano
2015-12-22 19:11 ` Shawn Pearce
2015-12-22 19:34 ` Junio C Hamano
2015-12-23 4:59 ` Michael Haggerty
2015-12-24 1:33 ` Junio C Hamano [this message]
[not found] ` <4689734.cEcQ2vR0aQ@mfick1-lnx>
2015-12-22 20:56 ` Martin Fick
2015-12-22 21:23 ` Junio C Hamano
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=xmqqsi2sbpgz.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=dturner@twopensource.com \
--cc=git@vger.kernel.org \
--cc=mfick@codeaurora.org \
--cc=mhagger@alum.mit.edu \
--cc=peff@peff.net \
--cc=spearce@spearce.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.