Re: [MAINTAINERS SUMMIT] [4/4] Discuss how to better prevent backports of commits that turn out to cause regressions

Michael Ellerman
2024-06-15T11:29:59Z

Geert Uytterhoeven <geert@linux-m68k.org> writes:
> Hi Konstantin,
>
> On Fri, Jun 14, 2024 at 4:38 PM Konstantin Ryabitsev
> <konstantin@linuxfoundation.org> wrote:
>> On Sat, Jun 15, 2024 at 12:29:09AM GMT, Michael Ellerman wrote:
>> > > 1. disambiguates Link: trailers so they point to relevant online discussions
>> > > 2. allows tooling like b4, patchwork, etc, to reliably match commits to
>> > > submissions for the purposes of better code review automation
>> > > 3. allows stable and similar projects to better track series grouping for
>> > > commits
>> >
>> > Message-Id: sucks, I want a link I can open with a single click.
>>
>> But why would you want to, on a regular basis? Viewing the series submission
>> has got to provide near zero useful info -- if it was accepted into the tree,
>> then at most it would have a couple of stray code review trailers.
>
> I open these links regularly (as in daily), for various reasons:
> - Finding the thread to reply to when reporting a bug,
> - Checking for new Rb-tags given,
> - As a starting point for reading earlier submissions of the
> same patch,
> - ...

Yep, all those.

I also use them to check that the version of a patch I have committed
locally in my testing tree is still the latest submission, before
pushing. Because the time between applying a patch and pushing it can be
days if it needs lots of testing.

Another case from yesterday was a ~3 year old patch, someone was asking
about backporting. I opened the link to the submission and saw that
someone had replied to it reporting a bug (that I had forgotten about).

cheers