From: Jani Nikula <jani.nikula@linux.intel.com>
To: Jonathan Corbet <corbet@lwn.net>,
Hu Haowen <2023002089@link.tyut.edu.cn>
Cc: Hu Haowen <2023002089@link.tyut.edu.cn>,
src.res.211@gmail.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs/zh_TW: replace my email address
Date: Mon, 23 Oct 2023 13:43:13 +0300 [thread overview]
Message-ID: <871qdld3ge.fsf@intel.com> (raw)
In-Reply-To: <87cyx6krb2.fsf@meer.lwn.net>
On Sun, 22 Oct 2023, Jonathan Corbet <corbet@lwn.net> wrote:
> Jonathan Corbet <corbet@lwn.net> writes:
>
>> Hu Haowen <2023002089@link.tyut.edu.cn> writes:
>>
>>> The Gmail address will not be used often from now on, and replace it
>>> with the email which is more frequently accessed by myself.
>>>
>>> Signed-off-by: Hu Haowen <2023002089@link.tyut.edu.cn>
>>
>> Applied.
>
> Actually, no:
>
> Documentation/translations/zh_TW/dev-tools/sparse.rst:10: WARNING: Title underline too short.
>
> Traditional Chinese maintainer: Hu Haowen <2023002089@link.tyut.edu.cn>
> ---------------------------------------------------------------------
My question is, why do the documents have inline
author/maintainer/translator information in them?
We have git log and MAINTAINERS for all of that?
BR,
Jani.
>
> Unapplied.
>
> Please do not send me anything for a while, at least until you have
> worked out a process that does not make me find the problems you are
> adding with each patch.
>
> jon
>
--
Jani Nikula, Intel
next prev parent reply other threads:[~2023-10-23 10:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 13:00 [PATCH] docs/zh_TW: replace my email address Hu Haowen
2023-10-23 2:15 ` Jonathan Corbet
2023-10-23 2:26 ` Jonathan Corbet
2023-10-23 10:43 ` Jani Nikula [this message]
2023-10-23 13:02 ` Jonathan Corbet
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=871qdld3ge.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=2023002089@link.tyut.edu.cn \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=src.res.211@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.