On Tue, Jul 12, 2016 at 5:26 PM, Jeff King <peff@xxxxxxxx> wrote: > Likewise for other per-worktree items. If we used refs/MERGE_HEAD and > refs/worktree/foo/MERGE_HEAD, then you could access them independently > by using the fully qualified names. I'm not opposed to letting one worktree see everything, but this move makes it harder to write new scripts (or new builtin commands, even) that works with both single and multiple worktrees because you refer to one ref (in current worktree perspective) differently. If we kill of the main worktree (i.e. git init always creates a linked worktree) then it's less of a problem, but still a nuisance to write refs/worktree/$CURRENT/<something> everywhere. > The only downside I see is that the existing names are sometimes > well-known. I wonder if we could simply add: > > refs/worktree/<your-worktree>/%s > > to the dwim ref-lookup when a command is running in a worktree. -- Duy -- 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