Re: RefTree: Alternate ref backend

From: Junio C Hamano <gitster@pobox.com>
Date: Dec 22, 2015, 21:23 UTC
Message-ID: <xmqqoadich4x.fsf@gitster.mtv.corp.google.com>
In-Reply-To: <6263203.WlZuyGWxlh@mfick1-lnx>

Martin Fick <mfick@codeaurora.org> writes:

Show 8 quoted lines

> ...  What if we added
> a leading slash for absolute references? Then I could do
> something like:
>
> /HEAD
> /refs/heads/master
> /refs/tags/v1.0.0
> /refs/remotes/origin/master

Yeah, that is one way to allow a tool to be absolutely certain there is no funny DWIMmery going on.

> This is a long term idea, but it might make sense to
> consider it now just for the sake of storing refs, it would
> eliminate the need for the ".." notation for "refs/..HEAD".

I do not see how the absolute notation has anything to do with eliminating "the need for the '..' notation" at all, though.

The funny "..HEAD" was brought up only because Shawn wanted to omit a single level of dereferencing of a tree object, so that the top-level tree for his ref backend would have "heads/", "tags/", etc. in it, and because "HEAD" is not next to "heads/" and "tags/", it needed some funny notation to avoid squatting on "HEAD" that should mean "refs/HEAD" in the notation.

> Now if we could only figure out a way to tell plumbing that
> something is a SHA, not a ref? :)

You do not need :) there; I think we discussed something along that line in the past few weeks (see the list archive).