From: "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
To: git@vger.kernel.org
Cc: ernesto.alfonsogonzalez@ge.com,
"Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
Subject: [PATCH] remote.c: specify correct plural form in "commit diverge" message
Date: Tue, 3 May 2016 07:12:30 +0700 [thread overview]
Message-ID: <1462234350-30902-1-git-send-email-pclouds@gmail.com> (raw)
In-Reply-To: <2A734D896A45164C887E476E942BF4F9B5F721@CINMBCNA09.e2k.ad.ge.com>
We need to count both "ours" and "theirs" commits when selecting plural
form for this message. Note that even though in this block, both ours
and theirs must be positive (i.e. can't be in singular form), we still
keep Q_(singular, plural) because languages other than English may have
more than one plural form.
Reported-by: Alfonsogonzalez, Ernesto (GE Digital) <ernesto.alfonsogonzalez@ge.com>
Signed-off-by: Nguyễn Thái Ngọc Duy <pclouds@gmail.com>
---
remote.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/remote.c b/remote.c
index 28fd676..212426e 100644
--- a/remote.c
+++ b/remote.c
@@ -2108,7 +2108,7 @@ int format_tracking_info(struct branch *branch, struct strbuf *sb)
"Your branch and '%s' have diverged,\n"
"and have %d and %d different commits each, "
"respectively.\n",
- theirs),
+ ours + theirs),
base, ours, theirs);
if (advice_status_hints)
strbuf_addf(sb,
--
2.8.0.rc0.210.gd302cd2
next prev parent reply other threads:[~2016-05-03 0:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-02 22:46 bug: incorrect plurality of "commit" in git status Alfonsogonzalez, Ernesto (GE Digital)
2016-05-03 0:12 ` Nguyễn Thái Ngọc Duy [this message]
2016-05-03 0:16 ` [PATCH] remote.c: specify correct plural form in "commit diverge" message Stefan Beller
2016-05-03 0:20 ` Duy Nguyen
2016-05-03 4:20 ` Jeff King
2016-05-03 4:43 ` Duy Nguyen
2016-05-03 4:48 ` Jeff King
2016-05-03 9:32 ` Duy Nguyen
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=1462234350-30902-1-git-send-email-pclouds@gmail.com \
--to=pclouds@gmail.com \
--cc=ernesto.alfonsogonzalez@ge.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).