From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: git@vger.kernel.org, "Johannes Sixt" <j6t@kdbg.org>,
"René Scharfe" <l.s.r@web.de>,
"Jean-Noël Avila" <jn.avila@free.fr>
Subject: Re: [PATCH 2/2] advice: refactor "action is not possible because you have unmerged files"
Date: Wed, 19 Jan 2022 16:31:57 +0100 [thread overview]
Message-ID: <220119.86tudzn3i0.gmgdl@evledraar.gmail.com> (raw)
In-Reply-To: <20220119094445.15542-3-bagasdotme@gmail.com>
On Wed, Jan 19 2022, Bagas Sanjaya wrote:
> Factor action names (cherry-picking, committing, merging, pulling, and
> reverting) out of the message string.
>
> Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
> ---
> advice.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/advice.c b/advice.c
> index 1dfc91d176..4c72856478 100644
> --- a/advice.c
> +++ b/advice.c
> @@ -175,15 +175,15 @@ void list_config_advices(struct string_list *list, const char *prefix)
> int error_resolve_conflict(const char *me)
> {
> if (!strcmp(me, "cherry-pick"))
> - error(_("Cherry-picking is not possible because you have unmerged files."));
> + error(_("%s is not possible because you have unmerged files."), "Cherry-picking");
> else if (!strcmp(me, "commit"))
> - error(_("Committing is not possible because you have unmerged files."));
> + error(_("%s is not possible because you have unmerged files."), "Commiting");
> else if (!strcmp(me, "merge"))
> - error(_("Merging is not possible because you have unmerged files."));
> + error(_("%s is not possible because you have unmerged files."), "Merging");
> else if (!strcmp(me, "pull"))
> - error(_("Pulling is not possible because you have unmerged files."));
> + error(_("%s is not possible because you have unmerged files."), "Pulling");
> else if (!strcmp(me, "revert"))
> - error(_("Reverting is not possible because you have unmerged files."));
> + error(_("%s is not possible because you have unmerged files."), "Reverting");
> else
> error(_("It is not possible to %s because you have unmerged files."),
> me);
René correctly notes downthread that we shouldn't change this, we have
plenty of these in git now to make these translatable to multiple
languages.
Just a tip that if you are refactoring something like this in that way
and we should change it, this is much nicer:
error(_("%s is not possible because you have unmerged files."),
!strcmp(me, "cherry-pick") ? "Cherry-picking" :
!strcmp(me, "commit") ? "Committing" :
[...]
I.e. if we could do your proposed de-duplication we can also
de-duplicate this whole else if chain in favor of a less verbose ternary
operation.
next prev parent reply other threads:[~2022-01-19 15:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-19 9:44 [PATCH 0/2] More similar messages refactoring Bagas Sanjaya
2022-01-19 9:44 ` [PATCH 1/2] sequencer: factor GIT_AUTHOR_* from message strings Bagas Sanjaya
2022-02-11 20:26 ` Jean-Noël AVILA
2022-01-19 9:44 ` [PATCH 2/2] advice: refactor "action is not possible because you have unmerged files" Bagas Sanjaya
2022-01-19 11:11 ` René Scharfe
2022-01-19 15:31 ` Ævar Arnfjörð Bjarmason [this message]
2022-01-19 15:42 ` Jean-Noël AVILA
2022-01-19 18:18 ` Junio C Hamano
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=220119.86tudzn3i0.gmgdl@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=bagasdotme@gmail.com \
--cc=git@vger.kernel.org \
--cc=j6t@kdbg.org \
--cc=jn.avila@free.fr \
--cc=l.s.r@web.de \
/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).