git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH 2/6] worktree: remove references to "git checkout --to" from the manpage

From
Michael Haggerty <mhagger@alum.mit.edu>
Date
Jul 19, 2015, 02:10 UTC
Message-ID
<58c91f8907d5f3ef91607e85a96adcf0b1278e14.1437271363.git.mhagger@alum.mit.edu>
In-Reply-To
<cover.1437271363.git.mhagger@alum.mit.edu>
Signed-off-by: Michael Haggerty <mhagger@alum.mit.edu>
---
 Documentation/git-worktree.txt | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
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).
-- 
2.1.4
Previous: Eric SunshineNext: Eric Sunshine
Message 4 of 14 in “Various tweaks to 'worktree'-related manpages”
  1. 0/6 Various tweaks to 'worktree'-related manpagesMichael Haggerty, Jul 19, 2015
  2. 1/6 worktree: consistently use term "linked working tree" in manpagesMichael Haggerty, Jul 19, 2015
  3. Eric SunshineJul 19, 2015
  4. 2/6 worktree: remove references to "git checkout --to" from the manpageMichael Haggerty, Jul 19, 2015
  5. Eric SunshineJul 19, 2015
  6. 3/6 worktree: fix incorrect references to file "locked"Michael Haggerty, Jul 19, 2015
  7. Eric SunshineJul 19, 2015
  8. 4/6 worktree: the "locked" mechanism is already implementedMichael Haggerty, Jul 19, 2015
  9. Eric SunshineJul 19, 2015
  10. 5/6 config.txt: refer to "git worktree prune", not "prune --worktree"Michael Haggerty, Jul 19, 2015
  11. Eric SunshineJul 19, 2015
  12. 6/6 worktree: wordsmith worktree-related manpagesMichael Haggerty, Jul 19, 2015
  13. Eric SunshineJul 19, 2015
  14. Eric SunshineJul 19, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.