From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: 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>
Cc: workflows@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
ksummit@lists.linux.dev
Subject: [PATCH 0/2] Documentation: update information for mailing lists
Date: Tue, 18 Jun 2024 12:42:09 -0400 [thread overview]
Message-ID: <20240618-docs-patch-msgid-link-v1-0-30555f3f5ad4@linuxfoundation.org> (raw)
There have been some important changes to the mailing lists hosted at
kernel.org, most importantly that vger.kernel.org was migrated from
majordomo+zmailer to mlmmj and is now being served from the unified
mailing list platform called "subspace" [1].
This series updates many links pointing at obsolete locations, but also
makes the following changes:
- drops the recommendation to use /r/ subpaths in lore.kernel.org links
(it has been unnecessary for a number of years)
- adds some detail on how to reference specific Link trailers from
inside the commit message
Some of these changes are the result of discussions on the ksummit
mailing list [2].
Link: https://subspace.kernel.org # [1]
Link: https://lore.kernel.org/20240617-arboreal-industrious-hedgehog-5b84ae@meerkat/ # [2]
Signed-off-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
---
Konstantin Ryabitsev (2):
Documentation: fix links to mailing list services
Documentation: best practices for using Link trailers
Documentation/process/2.Process.rst | 8 ++++----
Documentation/process/howto.rst | 10 +++++-----
Documentation/process/kernel-docs.rst | 5 ++---
Documentation/process/maintainer-netdev.rst | 5 ++---
Documentation/process/maintainer-tip.rst | 24 ++++++++++++++++++------
Documentation/process/submitting-patches.rst | 15 +++++----------
6 files changed, 36 insertions(+), 31 deletions(-)
---
base-commit: 6ba59ff4227927d3a8530fc2973b80e94b54d58f
change-id: 20240618-docs-patch-msgid-link-6961045516e0
Best regards,
--
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
next reply other threads:[~2024-06-18 16:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-18 16:42 Konstantin Ryabitsev [this message]
2024-06-18 16:42 ` [PATCH 1/2] Documentation: fix links to mailing list services Konstantin Ryabitsev
2024-06-18 18:15 ` Dan Williams
2024-06-22 20:11 ` Carlos Bilbao
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
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=20240618-docs-patch-msgid-link-v1-0-30555f3f5ad4@linuxfoundation.org \
--to=konstantin@linuxfoundation.org \
--cc=carlos.bilbao.osdev@gmail.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--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;
as well as URLs for NNTP newsgroup(s).