git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Dimitriy Ryazantcev <dimitriy.ryazantcev@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] l10n: minor case fix in 'git branch' '--unset-upstream' description
Date: Mon, 09 Dec 2019 12:30:31 -0800	[thread overview]
Message-ID: <xmqq4ky9utqw.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <20191208092647.7588-1-dimitriy.ryazantcev@gmail.com> (Dimitriy Ryazantcev's message of "Sun, 8 Dec 2019 11:26:47 +0200")

Dimitriy Ryazantcev <dimitriy.ryazantcev@gmail.com> writes:

> Signed-off-by: Dimitriy Ryazantcev <dimitriy.ryazantcev@gmail.com>
> ---
>  builtin/branch.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/builtin/branch.c b/builtin/branch.c
> index 2ef214632f..d8297f80ff 100644
> --- a/builtin/branch.c
> +++ b/builtin/branch.c
> @@ -624,7 +624,7 @@ int cmd_branch(int argc, const char **argv, const char *prefix)
>  		OPT_SET_INT_F(0, "set-upstream", &track, N_("do not use"),
>  			BRANCH_TRACK_OVERRIDE, PARSE_OPT_HIDDEN),
>  		OPT_STRING('u', "set-upstream-to", &new_upstream, N_("upstream"), N_("change the upstream info")),
> -		OPT_BOOL(0, "unset-upstream", &unset_upstream, N_("Unset the upstream info")),
> +		OPT_BOOL(0, "unset-upstream", &unset_upstream, N_("unset the upstream info")),
>  		OPT__COLOR(&branch_use_color, N_("use colored output")),
>  		OPT_SET_INT('r', "remotes",     &filter.kind, N_("act on remote-tracking branches"),
>  			FILTER_REFS_REMOTES),

Consistency is good.  Thanks.

      reply	other threads:[~2019-12-09 20:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-08  9:26 [PATCH] l10n: minor case fix in 'git branch' '--unset-upstream' description Dimitriy Ryazantcev
2019-12-09 20:30 ` Junio C Hamano [this message]

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=xmqq4ky9utqw.fsf@gitster-ct.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=dimitriy.ryazantcev@gmail.com \
    --cc=git@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).