[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <202406211355.4AF91C2@keescook>
Date: Fri, 21 Jun 2024 14:07:44 -0700
From: Kees Cook <kees@...nel.org>
To: Konstantin Ryabitsev <konstantin@...uxfoundation.org>
Cc: Jonathan Corbet <corbet@....net>,
Carlos Bilbao <carlos.bilbao.osdev@...il.com>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
workflows@...r.kernel.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
ksummit@...ts.linux.dev
Subject: Re: [PATCH v2 2/2] Documentation: best practices for using Link
trailers
On Wed, Jun 19, 2024 at 02:24:07PM -0400, Konstantin Ryabitsev wrote:
> + This URL should be used when referring to relevant mailing list
> + topics, related patch sets, or other notable discussion threads.
> + A convenient way to associate ``Link:`` trailers with the commit
> + message is to use markdown-like bracketed notation, for example::
> ...
> + Link: https://lore.kernel.org/some-msgid@here # [1]
> + Link: https://bugzilla.example.org/bug/12345 # [2]
Why are we adding the extra "# " characters? The vast majority of
existing Link tags don't do this:
$ git log --grep Link: | grep 'Link:.*\[' > links.txt
$ wc -l links.txt
1687 links.txt
# Link: URL... [1]
$ grep 'Link: .*[^#] \[' links.txt | wc -l
1546
# Link: URL... # [1]
$ grep 'Link: .* # \[' links.txt | wc -l
83
# Link: [1] URL...
$ grep 'Link: \[' links.txt | wc -l
44
# Link: URL... [#1]
$ grep 'Link: .*\[#' links.txt | wc -l
12
--
Kees Cook
Powered by blists - more mailing lists