[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87a54tabxg.fsf@trenco.lwn.net>
Date: Thu, 24 Jul 2025 08:41:31 -0600
From: Jonathan Corbet <corbet@....net>
To: Dongliang Mu <mudongliangabcd@...il.com>
Cc: Zhiyu Zhang <zhiyuzhang999@...il.com>, dzm91@...t.edu.cn,
si.yanteng@...ux.dev, linux-kernel@...r.kernel.org,
linux-doc@...r.kernel.org
Subject: Re: [PATCH] scripts: add origin commit identification based on
specific patterns
Dongliang Mu <mudongliangabcd@...il.com> writes:
> On Fri, Jul 18, 2025 at 4:09 AM Jonathan Corbet <corbet@....net> wrote:
>>
>> Zhiyu Zhang <zhiyuzhang999@...il.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@...il.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
Powered by blists - more mailing lists