From: Geert Stappers <stappers@stappers.nl>
To: "Miguel Ojeda" <ojeda@kernel.org>,
"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>,
"Andreas Hindborg" <a.hindborg@samsung.com>,
"Alice Ryhl" <aliceryhl@google.com>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
patches@lists.linux.dev
Subject: Re: [PATCH 1/2] MAINTAINERS: update Rust webpage
Date: Wed, 30 Aug 2023 19:53:09 +0200 [thread overview]
Message-ID: <ZO+CBdxxuDBrdDR8@gpm.stappers.nl> (raw)
In-Reply-To: <20230830165949.127475-1-ojeda@kernel.org>
On Wed, Aug 30, 2023 at 06:59:48PM +0200, Miguel Ojeda wrote:
> 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.
It looks like "mdbook" and "webbrowser view-source" confirms it is.
> 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://rust-for-linux.com [1]
Where to find the source for the MarkDownBook?
> 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://github.com/Rust-for-Linux/linux
> +W: https://rust-for-linux.com
> B: https://github.com/Rust-for-Linux/linux/issues
> C: zulip://rust-for-linux.zulipchat.com
> T: git https://github.com/Rust-for-Linux/linux.git rust-next
>
> base-commit: 4af84c6a85c63bec24611e46bb3de2c0a6602a51
> --
> 2.42.0
Reviewed-by: Geert Stappers <stappers@stappers.nl>
Groeten
Geert Stappers
--
Silence is hard to parse
next prev parent reply other threads:[~2023-08-30 18:03 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 ` Geert Stappers [this message]
2023-09-22 18:45 ` [PATCH 1/2] MAINTAINERS: update Rust webpage Miguel Ojeda
2023-09-02 18:57 ` Boqun Feng
2023-09-04 7:40 ` Andreas Hindborg
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=ZO+CBdxxuDBrdDR8@gpm.stappers.nl \
--to=stappers@stappers.nl \
--cc=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;
as well as URLs for NNTP newsgroup(s).