Michael Haggerty <mhagger@xxxxxxxxxxxx> 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. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html