Skip to content

Commit 4d5a3c5

Browse files
sunshinecogitster
authored andcommitted
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 <[email protected]> Signed-off-by: Junio C Hamano <[email protected]>
1 parent c925fe2 commit 4d5a3c5

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

Documentation/git-worktree.txt

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ DESCRIPTION
1818
Manage multiple worktrees attached to the same repository.
1919

2020
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
2222
tree is associated with the repository. This new working tree is called a
2323
"linked working tree" as opposed to the "main working tree" prepared by "git
2424
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
9999
$GIT_DIR/worktrees directory. The private sub-directory's name is usually
100100
the base name of the linked working tree's path, possibly appended with a
101101
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
103103
working tree in `/path/other/test-next` and also creates a
104104
`$GIT_DIR/worktrees/test-next` directory (or `$GIT_DIR/worktrees/test-next1`
105105
if `test-next` is already taken).

0 commit comments

Comments
 (0)