From: Jonathan Corbet <corbet@lwn.net>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
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>,
Dan Williams <dan.j.williams@intel.com>,
ksummit@lists.linux.dev
Subject: Re: [PATCH v2 0/2] Documentation: update information for mailing lists
Date: Wed, 03 Jul 2024 17:04:27 -0600 [thread overview]
Message-ID: <87y16irsas.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20240619-docs-patch-msgid-link-v2-0-72dd272bfe37@linuxfoundation.org>
Konstantin Ryabitsev <konstantin@linuxfoundation.org> writes:
> 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>
> ---
> Changes in v2:
> - Minor wording changes to text and commit messages based on feedback.
> - Link to v1: https://lore.kernel.org/r/20240618-docs-patch-msgid-link-v1-0-30555f3f5ad4@linuxfoundation.org
>
So I have gone ahead and applied this. There are some important changes
here that shouldn't miss the merge window, and we can argue about the #
marking with it in-tree.
I am rather amused, though, that b4 added a few extra tag lines:
> Link: https://example.com/somewhere.html optional-other-stuff
> Signed-off-by: Random Developer <rdevelop@company.com>
> [ Fixed formatting ]
> Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
I do believe I'll amend the changelog before pushing this one :)
Thanks,
jon
prev parent reply other threads:[~2024-07-03 23:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 18:24 Konstantin Ryabitsev
2024-06-19 18:24 ` [PATCH v2 1/2] Documentation: fix links to mailing list services Konstantin Ryabitsev
2024-06-19 18:24 ` [PATCH v2 2/2] Documentation: best practices for using Link trailers Konstantin Ryabitsev
2024-06-21 10:34 ` Michael S. Tsirkin
2024-06-21 21:07 ` Kees Cook
2024-06-21 21:37 ` Konstantin Ryabitsev
2024-06-26 23:13 ` Jonathan Corbet
2024-06-26 23:17 ` Randy Dunlap
2024-06-27 3:51 ` Thorsten Leemhuis
2024-06-27 4:24 ` Randy Dunlap
2024-06-28 14:52 ` Konstantin Ryabitsev
2024-06-28 18:32 ` Steven Rostedt
2024-06-22 4:27 ` Michael Ellerman
2024-06-22 14:40 ` Kees Cook
2024-06-22 15:15 ` Randy Dunlap
2024-06-22 20:13 ` [PATCH v2 0/2] Documentation: update information for mailing lists Carlos Bilbao
2024-07-02 20:47 ` Steven Rostedt
2024-07-03 23:04 ` Jonathan Corbet [this message]
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=87y16irsas.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=carlos.bilbao.osdev@gmail.com \
--cc=dan.j.williams@intel.com \
--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