git-worktree.txt: keep subcommand listing in alphabetical order
This is probably not the best order. But it makes it no-brainer to know where to insert new commands. At some point we might want to reorder at least the synopsis part again, grouping commonly use subcommands together. Signed-off-by: Nguyễn Thái Ngọc Duy <pclouds@gmail.com> Reviewed-by: Eric Sunshine <sunshine@sunshineco.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Nguyễn Thái Ngọc Duy committed
May 22, 2016 at 16:33 UTC
7b722d906bd5b32f3c7a63fb77835b38c1e04e4a
2 files changed
+6
-6
Documentation/git-worktree.txt
+5
-5
@@ -10,8 +10,8 @@ SYNOPSIS
10
--------
11
[verse]
12
'git worktree add' [-f] [--detach] [--checkout] [-b <new-branch>] <path> [<branch>]
13
-'git worktree prune' [-n] [-v] [--expire <expire>]
13
'git worktree list' [--porcelain]
14
+'git worktree prune' [-n] [-v] [--expire <expire>]
15
16
DESCRIPTION
17
-----------
@@ -54,10 +54,6 @@ If `<branch>` is omitted and neither `-b` nor `-B` nor `--detached` used,
54
then, as a convenience, a new branch based at HEAD is created automatically,
55
as if `-b $(basename <path>)` was specified.
56
57
-prune::
58
-
59
-Prune working tree information in $GIT_DIR/worktrees.
60
-
57
list::
58
59
List details of each worktree. The main worktree is listed first, followed by
@@ -65,6 +61,10 @@ each of the linked worktrees. The output details include if the worktree is
61
bare, the revision currently checked out, and the branch currently checked out
62
(or 'detached HEAD' if none).
63
64
+prune::
65
+
66
+Prune working tree information in $GIT_DIR/worktrees.
67
+
68
OPTIONS
69
-------
70
builtin/worktree.c
+1
-1
@@ -13,8 +13,8 @@
13
14
static const char * const worktree_usage[] = {
15
N_("git worktree add [<options>] <path> [<branch>]"),
16
- N_("git worktree prune [<options>]"),
16
N_("git worktree list [<options>]"),
17
+ N_("git worktree prune [<options>]"),
18
NULL
19
};
20