From: si.yanteng@linux.dev
To: "Dongliang Mu" <dzm91@hust.edu.cn>, "Alex Shi" <alexs@kernel.org>,
"Yanteng Si" <siyanteng@loongson.cn>,
"Jonathan Corbet" <corbet@lwn.net>
Cc: hust-os-kernel-patches@googlegroups.com,
linux-doc@vger.kernel.org, "Dongliang Mu" <dzm91@hust.edu.cn>,
"Cheng Ziqiu" <chengziqiu@hust.edu.cn>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] scripts: add scripts/checktransupdate.py
Date: Tue, 11 Jun 2024 13:39:17 +0000 [thread overview]
Message-ID: <2e4f9b46821d4f40eadca253496816060c862156@linux.dev> (raw)
In-Reply-To: <20240611131723.53515-1-dzm91@hust.edu.cn>
2024年6月11日 21:17, "Dongliang Mu" <dzm91@hust.edu.cn> 写到:
>
> The checktransupdate.py script helps track the translation status of
>
> the documentation in different locales, e.g., zh_CN and verify if
>
> these documenation is up-to-date. More specially, it uses `git log`
>
> commit to find the latest english commit from the translation commit
>
> (order by author date) and the latest english commits from HEAD. If
>
> differences occur, report the file and commits that need to be updated.
>
> Signed-off-by: Dongliang Mu <dzm91@hust.edu.cn>
>
> Signed-off-by: Cheng Ziqiu <chengziqiu@hust.edu.cn>
>
> ---
>
> v1->v2: revise the output format of git commits
>
> add some description and usage of this script
>
> scripts/checktransupdate.py | 203 ++++++++++++++++++++++++++++++++++++
>
> 1 file changed, 203 insertions(+)
>
> create mode 100755 scripts/checktransupdate.py
>
Reviewed-by: Yanteng Si <siyanteng@loongson.cn>
Thanks,
Yanteng
next prev parent reply other threads:[~2024-06-11 13:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-11 13:17 [PATCH v2] scripts: add scripts/checktransupdate.py Dongliang Mu
2024-06-11 13:39 ` si.yanteng [this message]
2024-06-12 1:34 ` Alex Shi
2024-06-12 21:27 ` Jonathan Corbet
2024-06-13 6:06 ` Dongliang Mu
2024-06-13 12:58 ` Jonathan Corbet
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=2e4f9b46821d4f40eadca253496816060c862156@linux.dev \
--to=si.yanteng@linux.dev \
--cc=alexs@kernel.org \
--cc=chengziqiu@hust.edu.cn \
--cc=corbet@lwn.net \
--cc=dzm91@hust.edu.cn \
--cc=hust-os-kernel-patches@googlegroups.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=siyanteng@loongson.cn \
/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).