linux-kernel - Re: [PATCH] Documentation/maintainer-tip: Update Link tag rules

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <30015043cd7d5e4e74962ffa44ad2f1dd26710f7.camel@intel.com>
Date: Thu, 11 Sep 2025 04:56:37 +0000
From: "Huang, Kai" <kai.huang@...el.com>
To: "bp@...nel.org" <bp@...nel.org>, "x86@...nel.org" <x86@...nel.org>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"bp@...en8.de" <bp@...en8.de>
Subject: Re: [PATCH] Documentation/maintainer-tip: Update Link tag rules


>  
> -   This URL should be used when referring to relevant mailing list
> -   topics, related patch sets, or other notable discussion threads.
> +   This URL should be used when referring to relevant mailing list topics,
> +   related patch sets, or other notable discussion threads.  Do not add a Link
> +   tag to simply point to the mail which became the upstream commit - the Link
> +   should contain interesting and otherwise relevant information regardling

s/regardling/regarding ?

> +   the evolution of the change or any related side-discussion. See
> +   https://lore.kernel.org/r/CAHk-=wh5AyuvEhNY9a57v-vwyr7EkPVRUKMPwj92yF_K0dJHVg@mail.gmail.com
> +   for more info.
> +
>     A convenient way to associate ``Link:`` trailers with the commit
>     message is to use markdown-like bracketed notation, for example::
>  
> +

This looks like an intended change?

>       A similar approach was attempted before as part of a different
>       effort [1], but the initial implementation caused too many
>       regressions [2], so it was backed out and reimplemented.
> @@ -389,15 +396,6 @@ following tag ordering scheme:
>       Link: https://lore.kernel.org/some-msgid@here # [1]
>       Link: https://bugzilla.example.org/bug/12345  # [2]
>  
> -   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
> -
>  Please do not use combined tags, e.g. ``Reported-and-tested-by``, as
>  they just complicate automated extraction of tags.
>