Re: Replacing Link trailers

[Geert Uytterhoeven <geert@linux-m68k.org>]

Hi Matthieu,

On Thu, 16 Oct 2025 at 14:35, Mathieu Desnoyers
<mathieu.desnoyers@efficios.com> wrote:
> On 2025-10-16 08:18, Greg KH wrote:
> [...]
> > Be it a link: or a message-id, or something else that I
> > can "set and forget" in my git hooks and so can all other maintainers.
>
> I can't help but keep thinking that we are trying to solve a problem
> that is fundamentally just about namespacing with needlessly complex
> technical solutions that will degrade the workflow of many maintainers
> across the span of the entire Linux software development process.
>
> The "Link:" tag is unfortunately a bag of holding for all sorts of
> links. So if Linus interprets the "Link:" tag as a link to relevant
> URLs with an implied meaning "see also" or "more relevant info
> here", then whatever else gets added under "Link:" with a different
> purpose is seen as noise.
>
> One possible solution would be to introduce a new tag such as
> "Link-Origin: https://..." or just "Origin: https://..." or
> whatever better name we can collectively come up with.
>
> That way the semantic should be obvious to everyone.

We already have a way to distinguish:
  - "Link: https://patch.msgid.link/... " for the original patch email,
  - "Link: https://lore.kernel.org/..." for e.g. the big upfront design
    discussion.

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds