From: Boqun Feng <boqun.feng@gmail.com>
To: rust-for-linux@vger.kernel.org
Cc: "Greg KH" <gregkh@linuxfoundation.org>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Wedson Almeida Filho" <wedsonaf@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH v2] rust: MAINTAINERS: Add the zulip link
Date: Fri, 27 Jan 2023 23:22:49 -0800 [thread overview]
Message-ID: <20230128072258.3384037-1-boqun.feng@gmail.com> (raw)
Zulip organization "rust-for-linux" has been created since about 2 years
ago[1], and proven to be a great place for Rust related discussion,
therefore add the information in MAINTAINERS file so that newcomers have
more options to find guide and help.
[1]: https://lore.kernel.org/rust-for-linux/CANiq72=xVaMQkgCA9rspjV8bhWDGqAn4x78B0_4U1WBJYj1PiA@mail.gmail.com/
Signed-off-by: Boqun Feng <boqun.feng@gmail.com>
---
v1 -> v2:
* As suggested by Greg KH, add commit message.
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 42fc47c6edfd..30161207f365 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -18219,6 +18219,7 @@ R: Boqun Feng <boqun.feng@gmail.com>
R: Gary Guo <gary@garyguo.net>
R: Björn Roy Baron <bjorn3_gh@protonmail.com>
L: rust-for-linux@vger.kernel.org
+C: zulip://rust-for-linux.zulipchat.com
S: Supported
W: https://github.com/Rust-for-Linux/linux
B: https://github.com/Rust-for-Linux/linux/issues
--
2.39.1
next reply other threads:[~2023-01-28 7:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-28 7:22 Boqun Feng [this message]
2023-01-28 10:29 ` [PATCH v2] rust: MAINTAINERS: Add the zulip link Vincenzo Palazzo
2023-02-01 1:38 ` Miguel Ojeda
2023-02-01 18:45 ` [PATCH v3] " Boqun Feng
2023-02-01 22:50 ` Miguel Ojeda
2023-02-02 7:27 ` Vincenzo Palazzo
2023-02-02 8:45 ` [PATCH v2] " Alice Ferrazzi
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=20230128072258.3384037-1-boqun.feng@gmail.com \
--to=boqun.feng@gmail.com \
--cc=alex.gaynor@gmail.com \
--cc=bjorn3_gh@protonmail.com \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.