On Sat, Jul 18, 2015 at 10:10 PM, Michael Haggerty <mhagger@xxxxxxxxxxxx> wrote: > Signed-off-by: Michael Haggerty <mhagger@xxxxxxxxxxxx> > --- > diff --git a/Documentation/git-worktree.txt b/Documentation/git-worktree.txt > index c8dd0e5..707dfd0 100644 > --- a/Documentation/git-worktree.txt > +++ b/Documentation/git-worktree.txt > @@ -18,7 +18,7 @@ DESCRIPTION > Manage multiple worktrees attached to the same repository. > > A git repository can support multiple working trees, allowing you to check > -out more than one branch at a time. With `git checkout --to` a new working > +out more than one branch at a time. With `git worktree add`, a new working > tree is associated with the repository. This new working tree is called a > "linked working tree" as opposed to the "main working tree" prepared by "git > 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 > $GIT_DIR/worktrees directory. The private sub-directory's name is usually > the base name of the linked working tree's path, possibly appended with a > number to make it unique. For example, when `$GIT_DIR=/path/main/.git` the > -command `git checkout --to /path/other/test-next next` creates the linked > +command `git worktree add /path/other/test-next next` creates the linked > working tree in `/path/other/test-next` and also creates a > `$GIT_DIR/worktrees/test-next` directory (or `$GIT_DIR/worktrees/test-next1` > if `test-next` is already taken). These fixes are already in 'master': 4d5a3c5 (Documentation/git-worktree: fix stale "git checkout --to" references, 2015-07-16) -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html