From: Jonathan Corbet <corbet@lwn.net>
To: Yanteng Si <siyanteng@loongson.cn>,
alexs@kernel.org, seakeel@gmail.com, bobwxc@email.cn,
tangyeechou@gmail.com
Cc: Yanteng Si <siyanteng@loongson.cn>,
chenhuacai@kernel.org, jiaxun.yang@flygoat.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
siyanteng01@gmail.com
Subject: Re: [PATCH v2 1/1] MAINTAINERS: Become the docs/zh_CN maintainer
Date: Tue, 17 May 2022 13:27:58 -0600 [thread overview]
Message-ID: <8735h8vu0x.fsf@meer.lwn.net> (raw)
In-Reply-To: <b0c1324d1d63846d700ab354446a6deaf30754c0.1652712771.git.siyanteng@loongson.cn>
Yanteng Si <siyanteng@loongson.cn> writes:
> It's time to become a maintainer of Chinese documentation, and Yanteng's plan
> is to help everyone with the utmost enthusiasm and patience.
>
> Signed-off-by: Yanteng Si <siyanteng@loongson.cn>
> Reviewed-by: Alex Shi <alexs@kernel.org>
> ---
> MAINTAINERS | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 9ce78f2275dc..ff1364d9f7cc 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -4649,6 +4649,7 @@ F: Documentation/dev-tools/checkpatch.rst
>
> CHINESE DOCUMENTATION
> M: Alex Shi <alexs@kernel.org>
> +M: Yanteng Si <siyanteng@loongson.cn>
> S: Maintained
> F: Documentation/translations/zh_CN/
I've applied this. I am curious, though: what is your sense for what
being designated a "maintainer" means? Do you envision something beyond
reviewing patches (for which an "R:" entry would be most appropriate)?
In any case, you help with the documentation is appreciated!
Thanks,
jon
P.S. There is normally no need to send a new version of a patch just to
pick up a tag; b4 makes that just work.
next prev parent reply other threads:[~2022-05-17 19:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 15:57 [PATCH v2 0/1] docs/zh_CN: add Yanteng to zh_CN maintainer Yanteng Si
2022-05-16 15:57 ` [PATCH v2 1/1] MAINTAINERS: Become the docs/zh_CN maintainer Yanteng Si
2022-05-17 19:27 ` Jonathan Corbet [this message]
2022-05-18 14:05 ` yanteng si
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=8735h8vu0x.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=alexs@kernel.org \
--cc=bobwxc@email.cn \
--cc=chenhuacai@kernel.org \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=seakeel@gmail.com \
--cc=siyanteng01@gmail.com \
--cc=siyanteng@loongson.cn \
--cc=tangyeechou@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).