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

[PATCH] builtin/log.c: proper use of usage description array

From
Matthias Ruester <matthias.ruester@gmail.com>
Date
Sep 14, 2014, 20:11 UTC
Message-ID
<1410725491-29789-1-git-send-email-matthias.ruester@gmail.com>
Signed-off-by: Matthias Ruester <matthias.ruester@gmail.com>
---
 builtin/log.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/builtin/log.c b/builtin/log.c
index e4d8122..e713618 100644
--- a/builtin/log.c
+++ b/builtin/log.c
@@ -38,8 +38,8 @@ static const char *fmt_patch_subject_prefix = "PATCH";
 static const char *fmt_pretty;
 
 static const char * const builtin_log_usage[] = {
-	N_("git log [<options>] [<revision range>] [[--] <path>...]\n")
-	N_("   or: git show [options] <object>..."),
+	N_("git log [<options>] [<revision range>] [[--] <path>...]"),
+	N_("git show [options] <object>..."),
 	NULL
 };
 
-- 
1.9.1
Message 1 of 1 in “builtin/log.c: proper use of usage description array”
  1. builtin/log.c: proper use of usage description arrayMatthias Ruester, Sep 14, 2014

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.