Hi, Stefan Beller wrote: > If I recall correctly, "worktree" is the feature/command, and > "working tree" is an instance in the file system, even when you only > have one working tree. I'm not sure I agree with this distinction. "worktree" is just a short name for "working tree". Unfortunately gitglossary(7) doesn't make this clear at all --- it uses the term worktree a few times (and appears to mean "working tree" when it does --- e.g. Pathspecs are used on the command line of [...] and many other commands to limit the scope of operations to some subset of the tree or worktree. ) but never defines it. [...] > --- a/Documentation/git-worktree.txt > +++ b/Documentation/git-worktree.txt > @@ -58,10 +58,10 @@ as if `-b $(basename <path>)` was specified. > > list:: > > -List details of each worktree. The main worktree is listed first, followed by > -each of the linked worktrees. The output details include if the worktree is > -bare, the revision currently checked out, and the branch currently checked out > -(or 'detached HEAD' if none). > +List details of each working tree. The main working tree is listed first, > +followed by each of the linked working trees. The output details include if > +the working tree is bare, the revision currently checked out, and the branch > +currently checked out (or 'detached HEAD' if none). The patch itself looks good. Thanks, Jonathan