lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8735h8vu0x.fsf@meer.lwn.net>
Date:   Tue, 17 May 2022 13:27:58 -0600
From:   Jonathan Corbet <corbet@....net>
To:     Yanteng Si <siyanteng@...ngson.cn>, alexs@...nel.org,
        seakeel@...il.com, bobwxc@...il.cn, tangyeechou@...il.com
Cc:     Yanteng Si <siyanteng@...ngson.cn>, chenhuacai@...nel.org,
        jiaxun.yang@...goat.com, linux-doc@...r.kernel.org,
        linux-kernel@...r.kernel.org, siyanteng01@...il.com
Subject: Re: [PATCH v2 1/1] MAINTAINERS: Become the docs/zh_CN maintainer

Yanteng Si <siyanteng@...ngson.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@...ngson.cn>
> Reviewed-by: Alex Shi <alexs@...nel.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@...nel.org>
> +M:	Yanteng Si <siyanteng@...ngson.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.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ