public inbox for linux-doc@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Haowen Hu <srcres258@furdevs.cn>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] docs/zh_TW: update personal information
Date: Tue, 24 Feb 2026 07:49:09 -0700	[thread overview]
Message-ID: <87pl5u19ju.fsf@trenco.lwn.net> (raw)
In-Reply-To: <201bfa5f-2826-4a31-a4e6-a4cbe4dc884e@furdevs.cn>

Haowen Hu <srcres258@furdevs.cn> writes:

>> And two of the handful of changes you made that year were ... changing
>> your email address in all of those files.
>
> Sure. Just want to keep things synced as exactly as possible, and so
> does the patch mean to be.

I will repeat what I was saying: all of those continually changing email
addresses are a maintenance pain.  I would really rather see a patch
removing them, leaving credit at the top-level index.rst, as I said
before. 

>> I don't think that all this churn this is reasonable, especially for a
>> translation that appears to have been abandoned.  So I don't really want
>> to apply this.  I would suggest you send me an alternative *removing*
>> that information from those files, optionally leaving a credit for past
>> work done in Documentation/translations/zh_TW/index.rst.  The question
>> of when this translation becomes too old and should just be removed can
>> be left for another day.
>
> OK, so do you mean this translation (zh_TW) is planned to be removed
> from the entire documentation?

There are no such plans at the moment, no.  But there does come a point
where a translation is so obsolete that it does more harm than good and
there are no prospects of it being updated.  

> I'm working on the update job currently
> for the translation to become modern, and you can have a review of my
> rework when this is done and the patch is sent. I really want these
> texts to be kept in the kernel documentation and they are able to
> receive a thorough update to be suitable toward the kernel nowadays.

If you are working to update them, I am glad to hear that.  Please do it
incrementally, rather than with one big patch, though.  When you have a
file updated, go ahead and send your work.

Thanks,

jon

  reply	other threads:[~2026-02-24 14:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-20 16:01 [PATCH 1/2] docs/zh_TW: update personal information Haowen Hu
2026-02-20 16:01 ` [PATCH 2/2] docs/zh_TW: remove trailing space Haowen Hu
2026-02-23 21:52   ` Jonathan Corbet
2026-02-23 21:51 ` [PATCH 1/2] docs/zh_TW: update personal information Jonathan Corbet
2026-02-24  3:03   ` Haowen Hu
2026-02-24 14:49     ` Jonathan Corbet [this message]
     [not found]   ` <7fee40fd-e9dd-4b45-88b0-67b6c3e228cd@furdevs.cn>
2026-02-24  3:11     ` Haowen Hu

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=87pl5u19ju.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=srcres258@furdevs.cn \
    /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