threads / patch / 16403

patchFix misleading wording for git-cherry-pick

Subject: [PATCH] Fix misleading wording for git-cherry-pick

## tl;dr

One message between Nov 20, 2008 and Nov 20, 2008. Diffs are folded; open one to read it.

replies: 0people: 1as markdown or json

Bryan Drewery· Nov 20, 2008, 05:11 UTC · lore

Documentation for -n implies that -x is normally used, however this is no longer true.

Signed-off-by: Bryan Drewery <bryan@shatow.net>
---
 Documentation/git-cherry-pick.txt |   13 ++++++-------
 1 files changed, 6 insertions(+), 7 deletions(-)
Show changes to Documentation/git-cherry-pick.txt +6 −7
diff --git a/Documentation/git-cherry-pick.txt
b/Documentation/git-cherry-pick.txt
index 837fb08..b764130 100644
--- a/Documentation/git-cherry-pick.txt
+++ b/Documentation/git-cherry-pick.txt
@@ -55,13 +55,12 @@ OPTIONS

 -n::
 --no-commit::
-	Usually the command automatically creates a commit with
-	a commit log message stating which commit was
-	cherry-picked.  This flag applies the change necessary
-	to cherry-pick the named commit to your working tree
-	and the index, but does not make the commit.  In addition,
-	when this option is used, your index does not have to match
-	the HEAD commit.  The cherry-pick is done against the
+	Usually the command automatically creates a commit.
+	This flag applies the change necessary to cherry-pick
+	the named commit to your working tree and the index,
+	but does not make the commit.  In addition, when this
+	option is used, your index does not have to match the
+	HEAD commit.  The cherry-pick is done against the
 	beginning state of your index.
 +
 This is useful when cherry-picking more than one commits'
-- 
1.5.6.4

← back to recent threads