From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Leon Romanovsky <leon@kernel.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 10:24:59 -0400 [thread overview]
Message-ID: <20240619-nostalgic-collie-of-glory-d7eb6e@lemur> (raw)
In-Reply-To: <20240619071251.GI4025@unreal>
On Wed, Jun 19, 2024 at 10:12:51AM GMT, Leon Romanovsky wrote:
> Default b4.linkmask points to https://msgid.link/ and not to https://patch.msgid.link/
That's the default for the b4 project itself, though, not the global default.
> https://git.kernel.org/pub/scm/utils/b4/b4.git/tree/.b4-config#n3
> https://git.kernel.org/pub/scm/utils/b4/b4.git/tree/docs/config.rst#n46
>
> It will be good to update the default value in b4 to point to the correct domain.
Once the series is accepted and becomes the official documentation, I will be
happy to change the global default.
-K
next prev parent reply other threads:[~2024-06-19 14:25 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 [this message]
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=20240619-nostalgic-collie-of-glory-d7eb6e@lemur \
--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=leon@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