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

[PATCH] cherry-pick/revert: make usage say '<commit-ish>...'

From
Kevin Bracey <kevin@bracey.fi>
Date
Apr 22, 2013, 15:57 UTC
Message-ID
<1366646257-27648-1-git-send-email-kevin@bracey.fi>

The usage string for cherry-pick and revert has never been updated to reflect their ability to handle multiple commits. Other documentation is already correct.

Signed-off-by: Kevin Bracey <kevin@bracey.fi>
---
 builtin/revert.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/builtin/revert.c b/builtin/revert.c
index c5e36b9..0401fdb 100644
--- a/builtin/revert.c
+++ b/builtin/revert.c
@@ -19,13 +19,13 @@
  */
 
 static const char * const revert_usage[] = {
-	N_("git revert [options] <commit-ish>"),
+	N_("git revert [options] <commit-ish>..."),
 	N_("git revert <subcommand>"),
 	NULL
 };
 
 static const char * const cherry_pick_usage[] = {
-	N_("git cherry-pick [options] <commit-ish>"),
+	N_("git cherry-pick [options] <commit-ish>..."),
 	N_("git cherry-pick <subcommand>"),
 	NULL
 };
-- 
1.8.2.255.g39c5835
Message 1 of 1 in “cherry-pick/revert: make usage say '<commit-ish>...'”
  1. cherry-pick/revert: make usage say '<commit-ish>...'Kevin Bracey, Apr 22, 2013

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.