From: Jiang Xin <worldhello.net@gmail.com>
To: "Trần Ngọc Quân" <vnwildman@gmail.com>
Cc: "Git l10n discussion group" <git-l10n@googlegroups.com>,
"Alexander Shopov" <ash@kambanaria.org>,
"Jordi Mas" <jmas@softcatala.org>,
"Matthias Rüster" <matthias.ruester@gmail.com>,
"Jimmy Angelakos" <vyruss@hellug.gr>,
"Christopher Díaz" <christopher.diaz.riv@gmail.com>,
"Jean-Noël Avila" <jn.avila@free.fr>,
"Bagas Sanjaya" <bagasdotme@gmail.com>,
"Alessandro Menti" <alessandro.menti@alessandromenti.it>,
"Gwan-gyeong Mun" <elongbug@gmail.com>, Arusekk <arek_koz@o2.pl>,
"Daniel Santos" <dacs.git@brilhante.top>,
"Dimitriy Ryazantcev" <DJm00n@mail.ru>,
"Peter Krefting" <peter@softwolves.pp.se>,
"Emir SARI" <bitigchi@me.com>, "Fangyi Zhou" <me@fangyi.io>,
"Yi-Jyun Pan" <pan93412@gmail.com>,
"Git List" <git@vger.kernel.org>
Subject: Re: [L10N] Kickoff for Git 2.37.0 round #1
Date: Sun, 19 Jun 2022 20:13:58 +0800 [thread overview]
Message-ID: <CANYiYbGWoMpCOA43k=5a_kio2thf91BV69nfSySwhHZbbMOSkg@mail.gmail.com> (raw)
In-Reply-To: <CAPv0VGvKFEbVzZEdn+eb-4Bb9KfQWCa=pM3iC_Dyu-6AKGCcug@mail.gmail.com>
On Sun, Jun 19, 2022 at 4:02 PM Trần Ngọc Quân <vnwildman@gmail.com> wrote:
>
> On Tue, Jun 14, 2022 at 6:29 PM Jiang Xin <worldhello.net@gmail.com> wrote:
> >
> > Hi,
> >
> > Git v2.37.0-rc0 has been released, and it's time to start new round of
> > git l10n. This time there are 92 updated messages need to be translated
> > since last release. Please send your pull request to the l10n coordinator's
> > repository below before this update window closes on Sun, June 26, 2022.
> >
> > https://github.com/git-l10n/git-po/
> >
> Done, please pull!
>
> $ git log -n1 --stat
> commit 22262d3c1947626e296418ffa3543d3584995653 (HEAD -> master, origin/master,
> origin/HEAD)
> Author: Trần Ngọc Quân <vnwildman@gmail.com>
> Date: Sun Jun 19 07:48:40 2022 +0700
>
> l10n: vi(5367t): Updated Vietnamese translation v2.37
>
> Signed-off-by: Tran Ngoc Quan <vnwildman@gmail.com>
>
> po/vi.po | 37548 +++++++++++++++++++++++++++++++------------------------------
> 1 file changed, 19003 insertions(+), 18545 deletions(-)
You forgot to remove file-location comments in "po/vi.po". If you
send me pull request on GitHub, a CI workflow will be triggered to
execute the command below,
$ git-po-helper check-commits --github-action-event=push <rev-list-args>
and you will receive the following report:
------------------------------------------------------------------------------
INFO [po/vi.po@22262d3] 5367 条已翻译消息.
------------------------------------------------------------------------------
ERROR [po/vi.po@22262d3] Found file-location comments in po
file. By submitting a location-less
ERROR [po/vi.po@22262d3] "po/XX.po" file, the size of the Git
repository can be greatly reduced.
ERROR [po/vi.po@22262d3] See the discussion below:
ERROR [po/vi.po@22262d3]
ERROR [po/vi.po@22262d3]
https://lore.kernel.org/git/20220504124121.12683-1-worldhello.net@gmail.com/
ERROR [po/vi.po@22262d3]
ERROR [po/vi.po@22262d3] As how to commit a location-less
"po/XX.po" file, See:
ERROR [po/vi.po@22262d3]
ERROR [po/vi.po@22262d3] the [Updating a "XX.po" file]
section in "po/README.md"
------------------------------------------------------------------------------
WARNING commit 22262d3: subject length 53 > 50, about 63% commits have
a subject less than 50 characters
INFO checking commits: 0 passed, 1 failed.
------------------------------------------------------------------------------
INFO update pot file by running: make pot
ERROR: fail to execute "git-po-helper check-commits"
Will turn on the switch for file-location checking by default in
git-po-helper check-po, check-command, etc.
--
Jiang Xin
next prev parent reply other threads:[~2022-06-19 13:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-14 11:28 [L10N] Kickoff for Git 2.37.0 round #1 Jiang Xin
2022-06-19 8:02 ` Trần Ngọc Quân
2022-06-19 12:13 ` Jiang Xin [this message]
2022-06-22 14:26 ` Peter Krefting
2022-06-23 1:12 ` Jiang Xin
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='CANYiYbGWoMpCOA43k=5a_kio2thf91BV69nfSySwhHZbbMOSkg@mail.gmail.com' \
--to=worldhello.net@gmail.com \
--cc=DJm00n@mail.ru \
--cc=alessandro.menti@alessandromenti.it \
--cc=arek_koz@o2.pl \
--cc=ash@kambanaria.org \
--cc=bagasdotme@gmail.com \
--cc=bitigchi@me.com \
--cc=christopher.diaz.riv@gmail.com \
--cc=dacs.git@brilhante.top \
--cc=elongbug@gmail.com \
--cc=git-l10n@googlegroups.com \
--cc=git@vger.kernel.org \
--cc=jmas@softcatala.org \
--cc=jn.avila@free.fr \
--cc=matthias.ruester@gmail.com \
--cc=me@fangyi.io \
--cc=pan93412@gmail.com \
--cc=peter@softwolves.pp.se \
--cc=vnwildman@gmail.com \
--cc=vyruss@hellug.gr \
/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).