Re: Replacing Link trailers

["Rafael J. Wysocki" <rafael@kernel.org>]

On Fri, Oct 17, 2025 at 11:31 AM Geert Uytterhoeven
<geert@linux-m68k.org> wrote:
>
> Hi Vlastimil,
>
> On Fri, 17 Oct 2025 at 10:44, Vlastimil Babka <vbabka@suse.cz> wrote:
> > On 10/17/25 04:27, Doug Anderson wrote:
> > > On Thu, Oct 16, 2025 at 12:09 PM James Bottomley
> > > <James.Bottomley@hansenpartnership.com> wrote:
> > >>
> > >> Since Linus' intervention this may be unnecessary,
> > >
> > > Thanks to a tip from LWN, connecting this thread to the other
> > > centithread on Link tags. Presumably this is what James meant about
> > > "Linus' intervention"?
> > >
> > > Link: https://lore.kernel.org/all/CAHk-=wj5MATvT-FR8qNpXuuBGiJdjY1kRfhtzuyBSpTKR+=Vtw@mail.gmail.com/
> > >
> > > As per standard Linux practices, please don't submit anything to
> > > "Documentation" about this. Anyone who needs to know should be able to
> > > find the current policy about Link: tags in the middle of a random
> > > centithread. ;-) "Use the <mailing lists>, Luke." ;-)
> >
> > The documentation has existed for a while in
> > Documentation/process/maintainer-tip.rst
> >
> >    You can also use ``Link:`` trailers to indicate the origin of the
> >    patch when applying it to your git tree. In that case, please use the
> >    dedicated ``patch.msgid.link`` domain instead of ``lore.kernel.org``.
> >    This practice makes it possible for automated tooling to identify
> >    which link to use to retrieve the original patch submission. For
> >    example::
> >
> >      Link: https://patch.msgid.link/patch-source-message-id@here
> >
> > Since that file is strictly speaking about the tip tree, it would make sense
> > to promote it to something more generic?
>
> That existed, too, but was removed in commit 944df7a31452f75b ("docs:
> update the guidance for Link: tags") in v6.18-rc1.  That commit carries
> a non-clickable Message-ID:-tag instead, and does not apply to Chinese
> readers ;-)

So I guess it can be restored in a more generic form (maybe along with
some specific examples of what that information is used for), but
instead of saying "In that case, please use the dedicated
``patch.msgid.link`` domain instead of ``lore.kernel.org``", I would
say "In that case, the dedicated ``patch.msgid.link`` domain must be
used instead of ``lore.kernel.org``".