From: Junio C Hamano <gitster@pobox.com>
To: Jiang Xin <worldhello.net@gmail.com>
Cc: Git l10n discussion group <git-l10n@googlegroups.com>,
Git List <git@vger.kernel.org>, Yi-Jyun Pan <pan93412@gmail.com>
Subject: Re: [GIT PULL] l10n updates for 2.41.0 round 2
Date: Thu, 01 Jun 2023 16:11:32 +0900 [thread overview]
Message-ID: <xmqqmt1jbqsb.fsf@gitster.g> (raw)
In-Reply-To: <20230601003151.26771-1-worldhello.net@gmail.com> (Jiang Xin's message of "Thu, 1 Jun 2023 08:31:51 +0800")
Jiang Xin <worldhello.net@gmail.com> writes:
> Hi Junio,
>
>> In this release we have a new l10n language, Ukrainian, thanks Arkadii
>> for contribution. L10n for Traditional Chinese is still in draft mode
>> at [1] and not ready to be merged yet. Maybe another update will be
>> sent tomorrow.
>>
>> [1] https://github.com/git-l10n/git-po/pull/712
>>
Wonderful. Will pull and use them in the release.
Thanks.
prev parent reply other threads:[~2023-06-01 7:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 0:31 [GIT PULL] l10n updates for 2.41.0 round 2 Jiang Xin
2023-06-01 7:11 ` Junio C Hamano [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=xmqqmt1jbqsb.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git-l10n@googlegroups.com \
--cc=git@vger.kernel.org \
--cc=pan93412@gmail.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 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).