All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiandong Qiu <qiujiandong1998@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>, alexs@kernel.org, si.yanteng@linux.dev
Cc: dzm91@hust.edu.cn, skhan@linuxfoundation.org,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] docs/zh_CN: add process/changes.rst translation
Date: Sat, 20 Jun 2026 00:25:34 +0800	[thread overview]
Message-ID: <e94bc823-0c2c-4cf4-8a17-a31e60fb77fb@gmail.com> (raw)
In-Reply-To: <87pl1mtxqc.fsf@trenco.lwn.net>

On 6/19/26 10:23 PM, Jonathan Corbet wrote:
> Here too, we don't need this label.
> 
> (Yes, I'm quibbling on details because I am in no position to judge the
> translation itself :)
Hi Jon,

Thank you for pointing this out.

I don't think this is quibbling at all; it sounds like a good cleanup to
me. I was following the structure of the original English document
closely, so I did not realize that these top-of-file labels were
something we should avoid now.

I will drop these labels in the next version and just refer to the files
by name where needed.

Thanks,
Jiandong

  reply	other threads:[~2026-06-19 16:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-19 14:02 [PATCH 0/3] docs/zh_CN: update translation of doc-guide/sphinx.rst Jiandong Qiu
2026-06-19 14:02 ` [PATCH 1/3] docs/zh_CN: add llvm.rst translation anchor Jiandong Qiu
2026-06-19 14:23   ` Jonathan Corbet
2026-06-19 14:02 ` [PATCH 2/3] docs/zh_CN: add process/changes.rst translation Jiandong Qiu
2026-06-19 14:23   ` Jonathan Corbet
2026-06-19 16:25     ` Jiandong Qiu [this message]
2026-06-19 14:02 ` [PATCH 3/3] docs/zh_CN: update sphinx.rst translation Jiandong Qiu
2026-06-19 14:26 ` [PATCH 0/3] docs/zh_CN: update translation of doc-guide/sphinx.rst Jonathan Corbet
2026-06-19 16:28   ` Jiandong Qiu

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=e94bc823-0c2c-4cf4-8a17-a31e60fb77fb@gmail.com \
    --to=qiujiandong1998@gmail.com \
    --cc=alexs@kernel.org \
    --cc=corbet@lwn.net \
    --cc=dzm91@hust.edu.cn \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=si.yanteng@linux.dev \
    --cc=skhan@linuxfoundation.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.