On Sat, Aug 22, 2015 at 11:51 PM, Michael Rappazzo <rappa...@gmail.com> wrote: > 'git worktree list' uses the for_each_worktree function to iterate, > and outputs in the format: '<worktree> (<short-ref>)' > > Signed-off-by: Michael Rappazzo <rappa...@gmail.com> > --- > Documentation/git-worktree.txt | 11 +++++- > builtin/worktree.c | 55 ++++++++++++++++++++++++++++ > t/t2027-worktree-list.sh | 81 > ++++++++++++++++++++++++++++++++++++++++++ > 3 files changed, 146 insertions(+), 1 deletion(-) > create mode 100755 t/t2027-worktree-list.sh > > diff --git a/Documentation/git-worktree.txt b/Documentation/git-worktree.txt > index fb68156..e953b4e 100644 > --- a/Documentation/git-worktree.txt > +++ b/Documentation/git-worktree.txt > @@ -11,6 +11,7 @@ SYNOPSIS > [verse] > 'git worktree add' [-f] [--detach] [-b <new-branch>] <path> [<branch>] > 'git worktree prune' [-n] [-v] [--expire <expire>] > +'git worktree list' [--path-only] > > DESCRIPTION > ----------- > @@ -59,6 +60,12 @@ prune:: > > Prune working tree information in $GIT_DIR/worktrees. > > +list:: > + > +List the main worktree followed by all of the linked worktrees. The default > +format of the list includes the full path to the worktree and the branch or > +revision that the head of that worktree is currently pointing to.
Maybe just "and the branch or revision currently checked out in that worktree."? -- Mikael Magnusson -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
