Elijah Newren <newren@xxxxxxxxx> writes: > But testing just now, I think the pseudorefs are already per-worktree. > I just did a merge in a secondary worktree, and then observed from the > primary worktree that a .git/worktrees/<id>/MERGE_HEAD was created, > not a .git/MERGE_HEAD. (Maybe the glossary could just spell out that > these are under $GIT_DIR and _not_ $GIT_COMMON_DIR to avoid potential > confusion?) I actually think the longer-term direction is to describe that these are always per-worktree, without referring to $GIT_DIR or giving any hints that these may be represented as a file in the filesystem. That would leave the door open for the reftable backend to take them over as well as the normal refs.
