Documentation/git-worktree: fix stale "git checkout --to" references
These should have been changed to "git worktree add" by fc56361 (worktree: introduce "add" command, 2015-07-06. Signed-off-by: Eric Sunshine <sunshine@sunshineco.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Eric Sunshine committed
Jul 16, 2015 at 18:09 UTC
4d5a3c588480953bd94dcc68ff198ad78e562c46
1 file changed
+2
-2
Documentation/git-worktree.txt
+2
-2
@@ -18,7 +18,7 @@ DESCRIPTION
18
Manage multiple worktrees attached to the same repository.
19
20
A git repository can support multiple working trees, allowing you to check
21
-out more than one branch at a time. With `git checkout --to` a new working
21
+out more than one branch at a time. With `git worktree add` a new working
22
tree is associated with the repository. This new working tree is called a
23
"linked working tree" as opposed to the "main working tree" prepared by "git
24
init" or "git clone". A repository has one main working tree (if it's not a
@@ -99,7 +99,7 @@ Each linked working tree has a private sub-directory in the repository's
99
$GIT_DIR/worktrees directory. The private sub-directory's name is usually
100
the base name of the linked working tree's path, possibly appended with a
101
number to make it unique. For example, when `$GIT_DIR=/path/main/.git` the
102
-command `git checkout --to /path/other/test-next next` creates the linked
102
+command `git worktree add /path/other/test-next next` creates the linked
103
working tree in `/path/other/test-next` and also creates a
104
`$GIT_DIR/worktrees/test-next` directory (or `$GIT_DIR/worktrees/test-next1`
105
if `test-next` is already taken).