From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, "Jean-Noël Avila" <jn.avila@free.fr>
Subject: ja/i18n-common-messages (was: What's cooking in git.git (Feb 2022, #01; Thu, 3))
Date: Fri, 04 Feb 2022 13:29:11 +0100 [thread overview]
Message-ID: <220204.86iltu3jbm.gmgdl@evledraar.gmail.com> (raw)
In-Reply-To: <xmqqr18jnr2t.fsf@gitster.g>
On Thu, Feb 03 2022, Junio C Hamano wrote:
> * ja/i18n-common-messages (2022-01-31) 5 commits
> - i18n: fix some misformated placeholders in command synopsis
> - i18n: remove from i18n strings that do not hold translatable parts
> - i18n: factorize "invalid value" messages
> - SQUASH???
> - i18n: factorize more 'incompatible options' messages
>
> Unify more messages to help l10n.
>
> Will merge to 'next' after squashing the fix-up in.
> source: <pull.1123.v4.git.1643666870.gitgitgadget@gmail.com>
I had a comment on the API direction in parse-options.c, which I think
should be done differently, but I also think it would be fine to just
change it up later:
https://lore.kernel.org/git/220201.86a6fa9tmr.gmgdl@evledraar.gmail.com/
I replied to v2 instead of v4 due to some (now fixed) mail delays at the
time, but that comment still applies to the latest version.
next prev parent reply other threads:[~2022-02-04 12:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 5:22 What's cooking in git.git (Feb 2022, #01; Thu, 3) Junio C Hamano
2022-02-04 7:00 ` Eric Sunshine
2022-02-05 8:00 ` Junio C Hamano
2022-02-04 8:13 ` Opinions on merging questions (Was: What's cooking in git.git (Feb 2022, #01; Thu, 3)) Elijah Newren
2022-02-04 11:20 ` en/remerge-diff (was: Opinions on merging questions (Was: What's cooking in git.git (Feb 2022, #01; Thu, 3))) Ævar Arnfjörð Bjarmason
2022-02-04 16:42 ` en/remerge-diff Junio C Hamano
2022-02-06 11:41 ` Opinions on merging questions (Was: What's cooking in git.git (Feb 2022, #01; Thu, 3)) Eric Sunshine
2022-02-09 14:57 ` Derrick Stolee
2022-02-07 14:11 ` Phillip Wood
2022-02-04 11:25 ` jc/doc-log-messages (was: " Ævar Arnfjörð Bjarmason
2022-02-04 12:23 ` rj/receive-pack-abort-upon-disconnect " Ævar Arnfjörð Bjarmason
2022-02-04 12:25 ` cb/clear-quarantine-early-on-all-ref-update-errors " Ævar Arnfjörð Bjarmason
2022-02-04 16:45 ` cb/clear-quarantine-early-on-all-ref-update-errors Junio C Hamano
2022-02-04 12:29 ` Ævar Arnfjörð Bjarmason [this message]
2022-02-04 16:56 ` ja/i18n-common-messages Junio C Hamano
2022-02-05 12:18 ` ja/i18n-common-messages Jean-Noël AVILA
2022-02-06 8:12 ` ja/i18n-common-messages Bagas Sanjaya
2022-02-06 10:03 ` ja/i18n-common-messages Jean-Noël AVILA
2022-02-04 12:31 ` ps/avoid-unnecessary-hook-invocation-with-packed-refs (was: What's cooking in git.git (Feb 2022, #01; Thu, 3)) Ævar Arnfjörð Bjarmason
2022-02-04 12:36 ` ab/ambiguous-object-name " Ævar Arnfjörð Bjarmason
2022-02-04 13:05 ` tl/ls-tree-oid-only " Ævar Arnfjörð Bjarmason
2022-02-04 13:11 ` ab/only-single-progress-at-once " Ævar Arnfjörð Bjarmason
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=220204.86iltu3jbm.gmgdl@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jn.avila@free.fr \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).