From: Jonathan Nieder <jrnieder@gmail.com>
To: Phil Hord <hordp@cisco.com>
Cc: Git List <git@vger.kernel.org>,
Junio C Hamano <gitster@pobox.com>,
Ramkumar Ramachandra <artagnon@gmail.com>,
Phil Hord <phil.hord@gmail.com>
Subject: Re: [PATCH] cherry-pick: No advice to commit if --no-commit
Date: Tue, 21 Feb 2012 16:23:22 -0600 [thread overview]
Message-ID: <20120221222049.GA31934@burratino> (raw)
In-Reply-To: <1329858317-3066-1-git-send-email-hordp@cisco.com>
Hi Phil,
Phil Hord wrote:
> Signed-off-by: Phil Hord <hordp@cisco.com>
Thanks.
> +++ b/sequencer.c
[...]
> @@ -138,10 +138,12 @@ static void print_advice(int show_hint)
> return;
> }
>
> - if (show_hint)
> + if (show_hint) {
> advise(_("after resolving the conflicts, mark the corrected paths\n"
> - "with 'git add <paths>' or 'git rm <paths>'\n"
> - "and commit the result with 'git commit'"));
> + "with 'git add <paths>' or 'git rm <paths>'"));
> + if (!opts->no_commit)
> + advise(_( "and commit the result with 'git commit'"));
"cherry-pick --no-commit" was not about to commit, but the user might
have been. I think the hint is intended to convey that authorship
will be correctly preserved if the user continues with "git commit"
and no special -c option is necessary.
Could you say a little more about the motivation for this patch? For
example, did the existing message confuse someone, or was it grating
in the context of some particular workflow?
A smaller detail: splitting the message into two like this gives
translators less control over how to phrase the message and where to
wrap lines. Luckily that is easy to fix with
if (opts->no_commit)
advise(...);
else
advise(...);
which means more flexibility in phrasing the message with pertinent
advice for each case. ;-)
Ciao,
Jonathan
next prev parent reply other threads:[~2012-02-21 22:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-21 21:05 [PATCH] cherry-pick: No advice to commit if --no-commit Phil Hord
2012-02-21 22:23 ` Jonathan Nieder [this message]
2012-02-21 22:31 ` Junio C Hamano
2012-02-22 0:18 ` Phil Hord
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=20120221222049.GA31934@burratino \
--to=jrnieder@gmail.com \
--cc=artagnon@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hordp@cisco.com \
--cc=phil.hord@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 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).