From: Jonathan Corbet <corbet@lwn.net>
To: Weijie Yuan <wy@wyuan.org>, Chen-Yu Yeh <chenyou910331@gmail.com>
Cc: Alex Shi <alexs@kernel.org>, Dongliang Mu <dzm91@hust.edu.cn>,
Yanteng Si <si.yanteng@linux.dev>,
Hu Haowen <2023002089@link.tyut.edu.cn>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: update Traditional Chinese documentation maintainers
Date: Fri, 31 Jul 2026 07:02:46 -0600 [thread overview]
Message-ID: <87o6fn5n2h.fsf@trenco.lwn.net> (raw)
In-Reply-To: <amxHIcHC0vjcp5bG@wyuan.org>
Weijie Yuan <wy@wyuan.org> writes:
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 2f9472c1a090..60f77e7fd3f5 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -27460,10 +27460,11 @@ F: kernel/trace/trace_osnoise.c
>> F: kernel/trace/trace_sched_wakeup.c
>>
>> TRADITIONAL CHINESE DOCUMENTATION
>> +M: Chen-Yu Yeh <chenyou910331@gmail.com>
>> +M: Weijie Yuan <wy@wyuan.org>
>> M: Hu Haowen <2023002089@link.tyut.edu.cn>
>
> Agreed: Haowen is always welcomed :-)
Nonetheless, I'm not sure I see the value of listing a maintainer who
has not maintained for years; a move to CREDITS may be in order.
> I remembered Haowen sent a patch here [1] aiming to change his name and
> address to:
>
> Haowen Hu <srcres258@furdevs.cn>
>
> Can we pick it up here?, while it may also needs Haowen's double check..
>
> [1] https://lore.kernel.org/linux-doc/20260220160201.41149-1-srcres258@furdevs.cn/
I resisted that because it was the third time churning all of those
email addresses in all of those files. If we are going to address them
now, I think the best thing is to simply remove them.
Thanks,
jon
next prev parent reply other threads:[~2026-07-31 13:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 3:21 [PATCH] MAINTAINERS: update Traditional Chinese documentation maintainers Chen-Yu Yeh
2026-07-31 6:56 ` Weijie Yuan
2026-07-31 13:02 ` Jonathan Corbet [this message]
2026-07-31 15:45 ` Weijie Yuan
2026-07-31 17:45 ` Weijie Yuan
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=87o6fn5n2h.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=2023002089@link.tyut.edu.cn \
--cc=alexs@kernel.org \
--cc=chenyou910331@gmail.com \
--cc=dzm91@hust.edu.cn \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=si.yanteng@linux.dev \
--cc=wy@wyuan.org \
/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