From: Junio C Hamano <gitster@pobox.com>
To: Alexander Kuleshov <kuleshovmail@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] show-branch: Indentation for show-branch usage
Date: Thu, 08 Jan 2015 12:05:09 -0800 [thread overview]
Message-ID: <xmqqsifldone.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <1420740516-20836-1-git-send-email-kuleshovmail@gmail.com> (Alexander Kuleshov's message of "Fri, 9 Jan 2015 00:08:36 +0600")
Alexander Kuleshov <kuleshovmail@gmail.com> writes:
> Signed-off-by: Alexander Kuleshov <kuleshovmail@gmail.com>
> ---
s/Indentation for/line-wrap/, perhaps?
What the patch wants to do makes sense to me, but I haven't seen a
long multi-line string, each lines in which is terminated with "\n\"
in the source, fed to N_() macro anywhere else in the existing
codebase, which makes me a bit nervous.
Would writing it this way instead, i.e. making it more obvious where
each line begins and how long the indentation of subsequent lines are,
also work?
N_("git show-branch [-a|--all] ...\n"
" [--current] [--color[=<when>]] ...\n"
...
" [--no-name ...");
Or does it break N_() macro?
Thanks.
> builtin/show-branch.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/builtin/show-branch.c b/builtin/show-branch.c
> index 270e39c..2e60107 100644
> --- a/builtin/show-branch.c
> +++ b/builtin/show-branch.c
> @@ -6,7 +6,10 @@
> #include "parse-options.h"
>
> static const char* show_branch_usage[] = {
> - N_("git show-branch [-a|--all] [-r|--remotes] [--topo-order | --date-order] [--current] [--color[=<when>] | --no-color] [--sparse] [--more=<n> | --list | --independent | --merge-base] [--no-name | --sha1-name] [--topics] [(<rev> | <glob>)...]"),
> + 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>)...]"),
> N_("git show-branch (-g|--reflog)[=<n>[,<base>]] [--list] [<ref>]"),
> NULL
> };
next prev parent reply other threads:[~2015-01-08 20:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-08 18:08 [PATCH] show-branch: Indentation for show-branch usage Alexander Kuleshov
2015-01-08 20:05 ` Junio C Hamano [this message]
2015-01-08 20:27 ` Alexander Kuleshov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqsifldone.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=kuleshovmail@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.