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

[PATCH] show-branch: fix indentation of usage string

From
Ralf Thielow <ralf.thielow@gmail.com>
Date
Jan 20, 2015, 19:30 UTC
Message-ID
<1421782228-24005-1-git-send-email-ralf.thielow@gmail.com>
In-Reply-To
<CANYiYbGL4A+ut8NjKmq6U8ADVf2M9Lq-5DOG3qxbKBp5srtrJQ@mail.gmail.com>
Noticed-by: Jean-Noël Avila <jn.avila@free.fr>
Signed-off-by: Ralf Thielow <ralf.thielow@gmail.com>
---
Jiang Xin <worldhello.net@gmail.com> wrote:
> 2015-01-18 23:53 GMT+08:00 Jean-Noël AVILA <jn.avila@free.fr>:
> Yes, it's wrong to using mixed tabs and spaces in the message. It comes
> from commit v2.0.5-5-g9990273, and it should be fixed.
This also breaks the indentation of the command output.
 builtin/show-branch.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/builtin/show-branch.c b/builtin/show-branch.c
index 691eeda..365228a 100644
--- a/builtin/show-branch.c
+++ b/builtin/show-branch.c
@@ -7,9 +7,9 @@
 
 static const char* show_branch_usage[] = {
     N_("git show-branch [-a|--all] [-r|--remotes] [--topo-order | --date-order]\n"
-       "		       [--current] [--color[=<when>] | --no-color] [--sparse]\n"
-       "		       [--more=<n> | --list | --independent | --merge-base]\n"
-       "	       [--no-name | --sha1-name] [--topics] [(<rev> | <glob>)...]"),
+       "		[--current] [--color[=<when>] | --no-color] [--sparse]\n"
+       "		[--more=<n> | --list | --independent | --merge-base]\n"
+       "		[--no-name | --sha1-name] [--topics] [(<rev> | <glob>)...]"),
     N_("git show-branch (-g|--reflog)[=<n>[,<base>]] [--list] [<ref>]"),
     NULL
 };
-- 
2.3.0.rc0.211.g05e7197
Previous: Jiang XinNext: Junio C Hamano
Message 2 of 4 in “Re: [L10N] Startup of Git 2.3.0 l10n round 2”
  1. Jiang XinJan 18, 2015
  2. show-branch: fix indentation of usage stringRalf Thielow, Jan 20, 2015
  3. Junio C HamanoJan 21, 2015
  4. l10n: correct indentation of show-branch usageJiang Xin, Jan 21, 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.