public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Jani Nikula <jani.nikula@linux.intel.com>,
	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 07:02:15 -0600	[thread overview]
Message-ID: <87a5s9jxuw.fsf@meer.lwn.net> (raw)
In-Reply-To: <871qdld3ge.fsf@intel.com>

Jani Nikula <jani.nikula@linux.intel.com> writes:

> 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?

Yeah, I've wondered about that too...especially since this person last
changed all of those email addresses ... in July.  I chose not to start
that particular discussion, but simply removing those lines would be a
better change, IMO.

Thanks,

jon

      reply	other threads:[~2023-10-23 13:02 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
2023-10-23 13:02       ` Jonathan Corbet [this message]

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=87a5s9jxuw.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=2023002089@link.tyut.edu.cn \
    --cc=jani.nikula@linux.intel.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox