From: Dan Carpenter <dan.carpenter@linaro.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
Carlos Bilbao <carlos.bilbao.osdev@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
workflows@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
ksummit@lists.linux.dev
Subject: Re: [PATCH 2/2] Documentation: best practices for using Link trailers
Date: Wed, 19 Jun 2024 11:08:47 +0300 [thread overview]
Message-ID: <aef741d4-d6e0-41f1-8102-c63a0fc5d7e2@moroto.mountain> (raw)
In-Reply-To: <20240618-docs-patch-msgid-link-v1-2-30555f3f5ad4@linuxfoundation.org>
On Tue, Jun 18, 2024 at 12:42:11PM -0400, Konstantin Ryabitsev wrote:
> Based on multiple conversations, most recently on the ksummit mailing
> list [1], add some best practices for using the Link trailer, such as:
>
> - how to use markdown-like bracketed numbers in the commit message to
> indicate the corresponding link
> - when to use lore.kernel.org vs patch.msgid.link domains
You should add something to checkpatch to complain about patch.msgid.link
URLs. Those URLs should only be added by the committers, not the patch
authors.
regards,
dan carpenter
next prev parent reply other threads:[~2024-06-19 8:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-18 16:42 [PATCH 0/2] Documentation: update information for mailing lists Konstantin Ryabitsev
2024-06-18 16:42 ` [PATCH 2/2] Documentation: best practices for using Link trailers Konstantin Ryabitsev
2024-06-19 7:12 ` Leon Romanovsky
2024-06-19 14:24 ` Konstantin Ryabitsev
2024-06-19 8:08 ` Dan Carpenter [this message]
2024-06-19 8:41 ` Michael S. Tsirkin
2024-06-19 8:53 ` Michael S. Tsirkin
2024-06-19 8:50 ` Jani Nikula
2024-06-19 9:08 ` Michael S. Tsirkin
2024-06-20 8:45 ` Thorsten Leemhuis
2024-06-22 20:10 ` Carlos Bilbao
2024-06-25 21:27 ` Steven Rostedt
2024-06-26 8:12 ` Geert Uytterhoeven
2024-06-26 14:16 ` Konstantin Ryabitsev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aef741d4-d6e0-41f1-8102-c63a0fc5d7e2@moroto.mountain \
--to=dan.carpenter@linaro.org \
--cc=carlos.bilbao.osdev@gmail.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=konstantin@linuxfoundation.org \
--cc=ksummit@lists.linux.dev \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=workflows@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox