All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Shi <seakeel@gmail.com>
To: 葉宸佑 <chenyou910331@gmail.com>, "Weijie Yuan" <wy@wyuan.org>
Cc: Dongliang Mu <dzm91@hust.edu.cn>,
	Hu Haowen <2023002089@link.tyut.edu.cn>,
	Jonathan Corbet <corbet@lwn.net>,
	Shuah Khan <skhan@linuxfoundation.org>,
	Dongliang Mu <mudongliangabcd@gmail.com>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Yuchen Tian <cat@malon.dev>, Alex Shi <alexs@kernel.org>,
	Yanteng Si <si.yanteng@linux.dev>
Subject: Re: [PATCH v2] docs: zh_TW: process: localize terminologies and improve fluency in 8.Conclusion
Date: Tue, 14 Jul 2026 14:22:37 +0800	[thread overview]
Message-ID: <abd713e1-e415-4985-a358-359f20ffee4b@gmail.com> (raw)
In-Reply-To: <CAKspUhJTGXzM=UeKTTZYX69NttBuCnAezz=ZOM9imPWLSP5g9A@mail.gmail.com>



On 2026/7/14 03:47, 葉宸佑 wrote:
> Weijie: agreed, a zh_TW how-to (mirroring the zh_CN one, with the
> glossary referenced) looks like the natural follow-up once the first
> series settles the terminology. Adding it to the list.
> 
> So, to keep everything in one place, my understanding of the plan:
> 
> - Chen-Yu: terminology series for process/ (14 files), folding in the
>    pending 8.Conclusion changes, glossary included; adopt the
>    "update to commit HASH" convention from now on
> - Chen-Yu: read Jon's advice for new-language efforts (Spanish thread)
> - later: a zh_TW how-to document
> - Weijie: investigate which documents may not need translation;
>    monitor the CN/TW lists during the trial period
> - Dongliang: review; patches routed through Alex's tree (pending
>    Alex's confirmation)

It's ok. I will pick up tested and reviewed commit into my Chinese 
documents tree.

> 
> If I got anything wrong, please correct me -- otherwise I will get
> started on the series.
> 
> Thanks,


  reply	other threads:[~2026-07-14  6:22 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-03  8:25 [PATCH v2] docs: zh_TW: process: localize terminologies and improve fluency in 8.Conclusion Chen-Yu Yeh
2026-07-10  8:49 ` 葉宸佑
2026-07-10 13:00   ` Weijie Yuan
2026-07-10 13:07     ` Weijie Yuan
2026-07-10 13:15     ` Dongliang Mu
2026-07-10 18:01       ` 葉宸佑
2026-07-11 17:21         ` Weijie Yuan
2026-07-11 20:04           ` Jonathan Corbet
2026-07-12  5:15             ` Weijie Yuan
2026-07-12  4:33           ` Alex Shi
2026-07-12  7:23             ` Weijie Yuan
2026-07-13  2:44               ` 葉宸佑
2026-07-13  3:49                 ` Dongliang Mu
2026-07-13  5:33                 ` Weijie Yuan
2026-07-13  6:35                   ` 葉宸佑
2026-07-13  9:03                     ` 葉宸佑
2026-07-13  9:41                       ` Dongliang Mu
2026-07-13 10:23                         ` Weijie Yuan
2026-07-13 19:47                           ` 葉宸佑
2026-07-14  6:22                             ` Alex Shi [this message]
2026-07-14  7:42                             ` Weijie Yuan
2026-07-10 13:05   ` Dongliang Mu
2026-07-11  5:21     ` 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=abd713e1-e415-4985-a358-359f20ffee4b@gmail.com \
    --to=seakeel@gmail.com \
    --cc=2023002089@link.tyut.edu.cn \
    --cc=alexs@kernel.org \
    --cc=cat@malon.dev \
    --cc=chenyou910331@gmail.com \
    --cc=corbet@lwn.net \
    --cc=dzm91@hust.edu.cn \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mudongliangabcd@gmail.com \
    --cc=si.yanteng@linux.dev \
    --cc=skhan@linuxfoundation.org \
    --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 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.