From: Yanteng Si <siyanteng@loongson.cn>
To: corbet@lwn.net, 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: [PATCH v2 0/1] docs/zh_CN: add Yanteng to zh_CN maintainer
Date: Mon, 16 May 2022 23:57:47 +0800 [thread overview]
Message-ID: <cover.1652712771.git.siyanteng@loongson.cn> (raw)
V2:
* Pick Alex's Reviewed-by tag.
V1:
* Add Yanteng Si into MAINTAINERS.
Yanteng Si (1):
MAINTAINERS: Become the docs/zh_CN maintainer
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
--
2.27.0
next reply other threads:[~2022-05-16 15:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 15:57 Yanteng Si [this message]
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
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=cover.1652712771.git.siyanteng@loongson.cn \
--to=siyanteng@loongson.cn \
--cc=alexs@kernel.org \
--cc=bobwxc@email.cn \
--cc=chenhuacai@kernel.org \
--cc=corbet@lwn.net \
--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=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).