From: Joe Perches <joe@perches.com>
To: Siddharth Menon <simeddon@gmail.com>
Cc: rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org,
apw@canonical.com, ojeda@kernel.org
Subject: Re: [PATCH] scripts/checkpatch.pl: check for non-permalinks to Zulip
Date: Sun, 25 Aug 2024 15:23:42 -0700 [thread overview]
Message-ID: <f53fa069b9cc24a9552d54c7a004fe6d@perches.com> (raw)
In-Reply-To: <20240825221806.253575-1-simeddon@gmail.com>
On 2024-08-25 15:18, Siddharth Menon wrote:
> Zulip links to https://rust-for-linux.zulipchat.com can break in
> case of renaming the topic or channel if they are not a message
> links (which are permalinks).
Why should these links be used in the kernel at all?
next prev parent reply other threads:[~2024-08-25 22:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-25 22:18 [PATCH] scripts/checkpatch.pl: check for non-permalinks to Zulip Siddharth Menon
2024-08-25 22:23 ` Joe Perches [this message]
2024-08-25 22:39 ` BiscuitBobby
2024-08-26 19:57 ` Miguel Ojeda
2024-08-26 20:03 ` Miguel Ojeda
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=f53fa069b9cc24a9552d54c7a004fe6d@perches.com \
--to=joe@perches.com \
--cc=apw@canonical.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=simeddon@gmail.com \
/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).