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

[PATCH v3 5/5] git-checkout.txt: better docs for '--patch'

From
Valentin Haenel <valentin.haenel@gmx.de>
Date
May 5, 2011, 18:48 UTC
Message-ID
<1304621328-17184-5-git-send-email-valentin.haenel@gmx.de>
In-Reply-To
<1304621271-17107-1-git-send-email-valentin.haenel@gmx.de>
* Include '-p' in synopsis and options
* Include a link to the git-add manpage for a description of the patch-mode.
Signed-off-by: Valentin Haenel <valentin.haenel@gmx.de>
Helped-by: Jeff King <peff@peff.net>
Mentored-by: Junio C Hamano <gitster@pobox.com>
---
 Documentation/git-checkout.txt |    7 ++++---
 1 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/Documentation/git-checkout.txt b/Documentation/git-checkout.txt
index 1063f69..9d53582 100644
--- a/Documentation/git-checkout.txt
+++ b/Documentation/git-checkout.txt
@@ -12,7 +12,7 @@ SYNOPSIS
 'git checkout' [-q] [-f] [-m] [--detach] [<commit>]
 'git checkout' [-q] [-f] [-m] [[-b|-B|--orphan] <new_branch>] [<start_point>]
 'git checkout' [-f|--ours|--theirs|-m|--conflict=<style>] [<tree-ish>] [--] <paths>...
-'git checkout' --patch [<tree-ish>] [--] [<paths>...]
+'git checkout' -p|--patch [<tree-ish>] [--] [<paths>...]
 
 DESCRIPTION
 -----------
@@ -45,7 +45,7 @@ $ git checkout <branch>
 that is to say, the branch is not reset/created unless "git checkout" is
 successful.
 
-'git checkout' [--patch] [<tree-ish>] [--] <pathspec>...::
+'git checkout' [-p|--patch] [<tree-ish>] [--] <pathspec>...::
 
 	When <paths> or `--patch` are given, 'git checkout' does *not*
 	switch branches.  It updates the named paths in the working tree
@@ -183,7 +183,8 @@ the conflicted merge in the specified paths.
 	working tree (and if a <tree-ish> was specified, the index).
 +
 This means that you can use `git checkout -p` to selectively discard
-edits from your current working tree.
+edits from your current working tree. See the ``Interactive Mode''
+section of linkgit:git-add[1] to learn how to operate the `\--patch` mode.
 
 <branch>::
 	Branch to checkout; if it refers to a branch (i.e., a name that,
-- 
1.7.1
Previous: Valentin HaenelNext: Junio C Hamano
Message 18 of 23 in “config.txt: interactive.singlekey is used by...”
  1. config.txt: interactive.singlekey is used by...Valentin Haenel, Apr 30, 2011
  2. Jeff KingMay 1, 2011
  3. 0/5 better document 'interactive.singlekey'Valentin Haenel, May 2, 2011
  4. 1/5 config.txt: 'interactive.singlekey; is used by...Valentin Haenel, May 2, 2011
  5. 2/5 git-add.txt: document 'interactive.singlekey'Valentin Haenel, May 2, 2011
  6. Junio C HamanoMay 2, 2011
  7. Valentin HaenelMay 3, 2011
  8. Junio C HamanoMay 3, 2011
  9. git-add.txt: document 'add.ignoreErrors'Valentin Haenel, May 4, 2011
  10. 0/5 better document 'interactive.singlekey' and '--patch'Valentin Haenel, May 5, 2011
  11. 1/5 config.txt: 'interactive.singlekey; is used by...Valentin Haenel, May 5, 2011
  12. 2/5 git-add.txt: document 'interactive.singlekey'Valentin Haenel, May 5, 2011
  13. 3/5 git-reset.txt: better docs for '--patch'Valentin Haenel, May 5, 2011
  14. Junio C HamanoMay 5, 2011
  15. Valentin HaenelMay 5, 2011
  16. 3/5 git-reset.txt: better docs for '--patch'Valentin Haenel, May 5, 2011
  17. 4/5 git-stash.txt: better docs for '--patch'Valentin Haenel, May 5, 2011
  18. 5/5 git-checkout.txt: better docs for '--patch'Valentin Haenel, May 5, 2011
  19. Junio C HamanoMay 5, 2011
  20. Junio C HamanoMay 5, 2011
  21. 3/5 git-reset.txt: document 'interactive.singlekey'Valentin Haenel, May 2, 2011
  22. 4/5 git-stash.txt: document 'interactive.singlekey'Valentin Haenel, May 2, 2011
  23. 5/5 git-checkout.txt: document 'interactive.singlekey'Valentin Haenel, May 2, 2011

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.