On Fri, Feb 1, 2019 at 2:28 PM Eric Sunshine <[email protected]> wrote: > > On Fri, Feb 1, 2019 at 5:04 PM <[email protected]> wrote: > > Subject: branch: Add an extra verbose output displaying worktree path for > > refs checked out in a linked worktree > > Overlong subject. Perhaps shorten it to: > > branch: display worktree path in -v -v mode > > or something, and use the longer description as the rest of the body > of the commit message.
OK > > > Signed-off-by: Nickolai Belakovski <[email protected]> > > --- > > diff --git a/Documentation/git-branch.txt b/Documentation/git-branch.txt > > @@ -167,8 +167,10 @@ This option is only applicable in non-verbose mode. > > When in list mode, > > show sha1 and commit subject line for each head, along with > > relationship to upstream branch (if any). If given twice, print > > - the name of the upstream branch, as well (see also `git remote > > - show <remote>`). > > + the path of the linked worktree, if applicable (not applicable > > + for main worktree since user's path will already be in main > > + worktree) and the name of the upstream branch, as well (see also > > + `git remote show <remote>`). > > I'm not sure I understand the "not applicable" explanation. When you > say "user's path", do you mean the current working directory? What > happens if the command is invoked from within one of the linked > worktrees (not from within the main worktree)? I should correct that to say "current worktree" as opposed to main, since that's what HEAD will give. And yes user's path means cwd. Does that make more sense?
