patches.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Benno Lossin <benno.lossin@proton.me>
To: Miguel Ojeda <ojeda@kernel.org>,
	Wedson Almeida Filho <wedsonaf@gmail.com>,
	Alex Gaynor <alex.gaynor@gmail.com>
Cc: "Boqun Feng" <boqun.feng@gmail.com>,
	"Gary Guo" <gary@garyguo.net>,
	"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
	"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 2/2] MAINTAINERS: add Maintainer Entry Profile field for Rust
Date: Wed, 20 Sep 2023 13:27:32 +0000	[thread overview]
Message-ID: <42e03dc3-fe08-a32d-1db4-31cfb25b71c5@proton.me> (raw)
In-Reply-To: <20230830165949.127475-2-ojeda@kernel.org>

On 30.08.23 18:59, Miguel Ojeda wrote:
> The `P:` field allows a URI, and we have been adding information
> on how to contribute to the Rust subsystem to our webpage for a
> while now (and other relevant topics, e.g. branches, third-party
> crates, Rust unstable features...).
> 
> The webpage/document does not currently follow the headings of
> the Maintainer Entry Profile, but it does nevertheless answer
> some of the questions we have got so far from contributors and
> it covers partially some of the topics there.
> 
> Thus link to our "Contributing" document [1].
> 
> Link: https://rust-for-linux.com/contributing [1]
> Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
> ---
>   MAINTAINERS | 1 +
>   1 file changed, 1 insertion(+)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 7c8088e9a11b..a27b673b01c3 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -18561,6 +18561,7 @@ S:	Supported
>   W:	https://rust-for-linux.com
>   B:	https://github.com/Rust-for-Linux/linux/issues
>   C:	zulip://rust-for-linux.zulipchat.com
> +P:	https://rust-for-linux.com/contributing
>   T:	git https://github.com/Rust-for-Linux/linux.git rust-next
>   F:	Documentation/rust/
>   F:	rust/
> --
> 2.42.0
> 

Reviewed-by: Benno Lossin <benno.lossin@proton.me>



  parent reply	other threads:[~2023-09-20 13:27 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 [this message]
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
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=42e03dc3-fe08-a32d-1db4-31cfb25b71c5@proton.me \
    --to=benno.lossin@proton.me \
    --cc=a.hindborg@samsung.com \
    --cc=alex.gaynor@gmail.com \
    --cc=aliceryhl@google.com \
    --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).