mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Dongliang Mu <mudongliangabcd@gmail.com>
Cc: Zhiyu Zhang <zhiyuzhang999@gmail.com>,
	dzm91@hust.edu.cn, si.yanteng@linux.dev,
	linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH] scripts: add origin commit identification based on specific patterns
Date: Thu, 24 Jul 2025 08:41:31 -0600	[thread overview]
Message-ID: <87a54tabxg.fsf@trenco.lwn.net> (raw)
In-Reply-To: <CAD-N9QUBDeX2tU50i292Rm8MGeGZ9icnxkb1pAVDYi+SYCdefQ@mail.gmail.com>

Dongliang Mu <mudongliangabcd@gmail.com> writes:

> On Fri, Jul 18, 2025 at 4:09 AM Jonathan Corbet <corbet@lwn.net> wrote:
>>
>> Zhiyu Zhang <zhiyuzhang999@gmail.com> writes:
>>
>> > This patch adds the functionability to smartly identify origin commit
>> > of the translation by matching the following patterns in commit log:
>> > 1) update to commit HASH
>> > 2) Update the translation through commit HASH
>> > If no such pattern is found, script will obey the original workflow.
>> >
>> > Signed-off-by: Zhiyu Zhang <zhiyuzhang999@gmail.com>
>> > ---
>> >  scripts/checktransupdate.py | 38 ++++++++++++++++++++++++++++++++++++-
>> >  1 file changed, 37 insertions(+), 1 deletion(-)
>>
>> So I don't have any objection to this, but wouldn't mind hearing from
>> folks who actually use this script - has anybody else tested it out?
>
> I’ve tested this script, and the new origin commit tracking
> functionality is working effectively—it can reduce the number of
> commits requiring updates.

Great, thanks, I've applied it.

jon

  reply	other threads:[~2025-07-24 14:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-13 16:34 Zhiyu Zhang
2025-07-17 20:08 ` Jonathan Corbet
2025-07-18  0:24   ` Dongliang Mu
2025-07-24 14:41     ` Jonathan Corbet [this message]
2025-07-18  0:22 ` Dongliang Mu

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=87a54tabxg.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=dzm91@hust.edu.cn \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mudongliangabcd@gmail.com \
    --cc=si.yanteng@linux.dev \
    --cc=zhiyuzhang999@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

all inboxes | Powered by JetHome®