From: Andreas Hindborg <a.hindborg@samsung.com>
To: Miguel Ojeda <ojeda@kernel.org>
Cc: "Wedson Almeida Filho" <wedsonaf@gmail.com>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <benno.lossin@proton.me>,
"Alice Ryhl" <aliceryhl@google.com>,
"rust-for-linux@vger.kernel.org" <rust-for-linux@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"patches@lists.linux.dev" <patches@lists.linux.dev>
Subject: Re: [PATCH 1/2] MAINTAINERS: update Rust webpage
Date: Mon, 4 Sep 2023 07:40:01 +0000 [thread overview]
Message-ID: <87ttsatmi6.fsf@samsung.com> (raw)
In-Reply-To: <20230830165949.127475-1-ojeda@kernel.org>
Miguel Ojeda <ojeda@kernel.org> writes:
> A few months ago we started a webpage for the Rust subsystem and
> the overall Rust for Linux project [1].
>
> The current `W:` field of the Rust entry points to the GitHub
> repository, since originally we kept information in a `README.md`
> file that got rendered by GitHub when visiting that URL.
>
> That information was moved into the webpage and got expanded.
> The webpage is also nowadays the entry point to the project,
> and we pointed the "Website" GitHub metadata field to it.
>
> Thus update the `W:` field to point to the actual webpage.
>
> Link: https://protect2.fireeye.com/v1/url?k=f6de0e95-97551ba3-f6df85da-74fe485fffe0-40da65c741bc6c5c&q=1&e=b1890d46-d9fd-4c52-9067-813223d79978&u=https%3A%2F%2Frust-for-linux.com%2F [1]
> Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
> ---
> MAINTAINERS | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 12601a47c839..7c8088e9a11b 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -18558,7 +18558,7 @@ R: Andreas Hindborg <a.hindborg@samsung.com>
> R: Alice Ryhl <aliceryhl@google.com>
> L: rust-for-linux@vger.kernel.org
> S: Supported
> -W: https://protect2.fireeye.com/v1/url?k=562fa4e0-37a4b1d6-562e2faf-74fe485fffe0-41ef9448fbcb2236&q=1&e=b1890d46-d9fd-4c52-9067-813223d79978&u=https%3A%2F%2Fgithub.com%2FRust-for-Linux%2Flinux
> +W: https://protect2.fireeye.com/v1/url?k=9d6f1261-fce40757-9d6e992e-74fe485fffe0-96ce3590ad5e7466&q=1&e=b1890d46-d9fd-4c52-9067-813223d79978&u=https%3A%2F%2Frust-for-linux.com%2F
> B: https://protect2.fireeye.com/v1/url?k=bce0bede-dd6babe8-bce13591-74fe485fffe0-1eb20aae852614aa&q=1&e=b1890d46-d9fd-4c52-9067-813223d79978&u=https%3A%2F%2Fgithub.com%2FRust-for-Linux%2Flinux%2Fissues
> C: zulip://rust-for-linux.zulipchat.com
> T: git
> https://protect2.fireeye.com/v1/url?k=db2bb7f4-baa0a2c2-db2a3cbb-74fe485fffe0-2d91ea432710b07e&q=1&e=b1890d46-d9fd-4c52-9067-813223d79978&u=https%3A%2F%2Fgithub.com%2FRust-for-Linux%2Flinux.git
> rust-next
>
> base-commit: 4af84c6a85c63bec24611e46bb3de2c0a6602a51
I was about to complain about the strange link you put. It took me a few
seconds to realize what was going on.
Perhaps we should start signing the patches?
Best regards,
Andreas
next prev parent reply other threads:[~2023-09-04 7:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230830170041eucas1p139eda9d21701ab726a9b36751b819ada@eucas1p1.samsung.com>
2023-08-30 16:59 ` [PATCH 1/2] MAINTAINERS: update Rust webpage Miguel Ojeda
2023-08-30 16:59 ` [PATCH 2/2] MAINTAINERS: add Maintainer Entry Profile field for Rust Miguel Ojeda
2023-09-04 7:48 ` Andreas Hindborg (Samsung)
2023-09-16 10:53 ` Vincenzo Palazzo
2023-09-19 9:04 ` Alice Ryhl
2023-09-20 13:27 ` Benno Lossin
2023-08-30 17:53 ` [PATCH 1/2] MAINTAINERS: update Rust webpage Geert Stappers
2023-09-22 18:45 ` Miguel Ojeda
2023-09-02 18:57 ` Boqun Feng
2023-09-04 7:40 ` Andreas Hindborg [this message]
2023-09-04 14:45 ` Greg KH
2023-09-04 7:43 ` Andreas Hindborg (Samsung)
2023-09-16 10:52 ` Vincenzo Palazzo
2023-09-19 9:02 ` Alice Ryhl
2023-09-20 13:27 ` Benno Lossin
2023-10-05 16:12 ` 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=87ttsatmi6.fsf@samsung.com \
--to=a.hindborg@samsung.com \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=patches@lists.linux.dev \
--cc=rust-for-linux@vger.kernel.org \
--cc=wedsonaf@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