From: Yanteng Si <si.yanteng@linux.dev>
To: Jonathan Corbet <corbet@lwn.net>,
xu.xin16@zte.com.cn, alexs@kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, mudongliangabcd@gmail.com,
seakeel@gmail.com
Cc: wang.yaxin@zte.com.cn, fan.yu9@zte.com.cn, he.peilin@zte.com.cn,
tu.qiang35@zte.com.cn, qiu.yutan@zte.com.cn,
zhang.yunkai@zte.com.cn
Subject: Re: [PATCH linux-next v8 RESEND] Docs/zh_CN: Translate physical_memory.rst to Simplified Chinese
Date: Tue, 5 Nov 2024 09:54:36 +0800 [thread overview]
Message-ID: <641acef2-70f4-4172-9fa9-da0f5203a78e@linux.dev> (raw)
In-Reply-To: <87ikt294v6.fsf@trenco.lwn.net>
在 2024/11/5 03:27, Jonathan Corbet 写道:
> OK, I have applied this patch. A couple of comments for future reference:
>
> <xu.xin16@zte.com.cn> writes:
>
>> Update to commit 7332f9e45d2e("docs/mm: Physical Memory: Fix grammar")
> ...and this I don't understand at all; why do you need to reference that
> patch here?
We use it to mark the progress of the translation against
the original document. If we don't put this tag on at the
very beginning, when the translation falls behind the original
document for a while, we'll have to go through the whole
original document log from the very top downwards, which
is an enormous amount of work. On the other hand, the
checktransupdate.py also works based on this tag.
Yeah, this tag might seem a bit ambiguous. I think maybe
we could improve it? For example:
Trans_mark commit 7332f9e45d2e ("docs/mm: Physical Memory: Fix grammar")
Thanks,
Yanteng
>
> Thanks,
>
> jon
next prev parent reply other threads:[~2024-11-05 1:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-28 5:53 [PATCH linux-next v8 RESEND] Docs/zh_CN: Translate physical_memory.rst to Simplified Chinese xu.xin16
2024-11-04 19:27 ` Jonathan Corbet
2024-11-05 1:54 ` Yanteng Si [this message]
2024-11-05 14:47 ` Jonathan Corbet
2024-11-06 2:09 ` Yanteng Si
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=641acef2-70f4-4172-9fa9-da0f5203a78e@linux.dev \
--to=si.yanteng@linux.dev \
--cc=alexs@kernel.org \
--cc=corbet@lwn.net \
--cc=fan.yu9@zte.com.cn \
--cc=he.peilin@zte.com.cn \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mudongliangabcd@gmail.com \
--cc=qiu.yutan@zte.com.cn \
--cc=seakeel@gmail.com \
--cc=tu.qiang35@zte.com.cn \
--cc=wang.yaxin@zte.com.cn \
--cc=xu.xin16@zte.com.cn \
--cc=zhang.yunkai@zte.com.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;
as well as URLs for NNTP newsgroup(s).