From: Junio C Hamano <gitster@pobox.com>
Date: Thu, 24 Dec 2015 01:33:00 GMT
Subject: Re: RefTree: Alternate ref backend
Message-ID: <xmqqsi2sbpgz.fsf@gitster.mtv.corp.google.com>
In-Reply-To: <567A2A44.3050003@alum.mit.edu>

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.