From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Jiang Xin <worldhello.net@gmail.com>
Subject: jx/l10n-workflow-change (was: What's cooking in git.git (May 2022, #07; Wed, 25))
Date: Thu, 26 May 2022 20:57:07 +0200 [thread overview]
Message-ID: <220526.86mtf43yvo.gmgdl@evledraar.gmail.com> (raw)
In-Reply-To: <xmqqzgj41ya2.fsf@gitster.g>
On Thu, May 26 2022, Junio C Hamano wrote:
> * jx/l10n-workflow-change (2022-05-23) 8 commits
> - l10n: Document the new l10n workflow
> - Makefile: add "po-init" rule to initialize po/XX.po
> - Makefile: add "po-update" rule to update po/XX.po
> - po/git.pot: don't check in result of "make pot"
> - i18n CI: stop allowing non-ASCII source messages in po/git.pot
> - Makefile: have "make pot" not "reset --hard"
> - Makefile: generate "po/git.pot" from stable LOCALIZED_C
> - Makefile: sort "po/git.pot" by file location
>
> A workflow change for translators are being proposed.
>
> Will merge to 'next'?
> source: <20220523012531.4505-1-worldhello.net@gmail.com>
I'm happy with the current (posted today) version of it, and think it
should advance.
prev parent reply other threads:[~2022-05-26 18:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-26 8:41 What's cooking in git.git (May 2022, #07; Wed, 25) Junio C Hamano
2022-05-26 16:02 ` Victoria Dye
2022-05-26 17:23 ` Junio C Hamano
2022-05-26 18:02 ` Ævar Arnfjörð Bjarmason
2022-05-26 18:30 ` Victoria Dye
2022-05-26 18:40 ` Ævar Arnfjörð Bjarmason
2022-05-26 23:10 ` Junio C Hamano
2022-05-26 18:08 ` tb/cruft-packs (was Re: What's cooking in git.git (May 2022, #07; Wed, 25)) Taylor Blau
2022-05-26 18:10 ` What's cooking in git.git (May 2022, #07; Wed, 25) Taylor Blau
2022-05-26 20:17 ` Junio C Hamano
2022-05-26 18:11 ` tb/midx-race-in-pack-objects (was Re: What's cooking in git.git (May 2022, #07; Wed, 25)) Taylor Blau
2022-05-26 18:49 ` sg/build-gitweb (was: " Ævar Arnfjörð Bjarmason
2022-05-26 19:06 ` sg/build-gitweb Junio C Hamano
2022-05-26 18:51 ` jc/http-clear-finished-pointer (was: What's cooking in git.git (May 2022, #07; Wed, 25)) Ævar Arnfjörð Bjarmason
2022-05-26 19:37 ` Re* jc/http-clear-finished-pointer Junio C Hamano
2022-05-27 20:41 ` Johannes Schindelin
2022-05-27 21:35 ` Junio C Hamano
2022-06-01 7:26 ` Ævar Arnfjörð Bjarmason
2022-06-01 15:48 ` Junio C Hamano
2022-05-26 18:54 ` js/bisect-in-c (was: What's cooking in git.git (May 2022, #07; Wed, 25)) Ævar Arnfjörð Bjarmason
2022-05-26 19:38 ` js/bisect-in-c Junio C Hamano
2022-05-26 20:00 ` js/bisect-in-c Junio C Hamano
2022-05-27 12:52 ` js/bisect-in-c Ævar Arnfjörð Bjarmason
2022-05-26 18:57 ` Ævar Arnfjörð Bjarmason [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=220526.86mtf43yvo.gmgdl@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=worldhello.net@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.