Patrick Steinhardt <ps@xxxxxx> writes: > That's ultimately the reason why I don't want HEAD to look like a proper > ref. But doing the "refs/heads/.invalid" workaround shouldn't be too bad, > I guess. Isn't the reason why reftable backend initializes refs/heads to be a regular file exactly because we want to reject an attempt to create such a file on the filesystem, though?
