linux-kernel - Re: [PATCH linux-next v8 RESEND] Docs/zh_CN: Translate physical

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <9209f37c-e3e8-4390-9630-0157ed8eb690@linux.dev>
Date: Wed, 6 Nov 2024 10:09:13 +0800
From: Yanteng Si <si.yanteng@...ux.dev>
To: Jonathan Corbet <corbet@....net>, xu.xin16@....com.cn, alexs@...nel.org,
 linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
 mudongliangabcd@...il.com, seakeel@...il.com
Cc: wang.yaxin@....com.cn, fan.yu9@....com.cn, he.peilin@....com.cn,
 tu.qiang35@....com.cn, qiu.yutan@....com.cn, zhang.yunkai@....com.cn
Subject: Re: [PATCH linux-next v8 RESEND] Docs/zh_CN: Translate
 physical_memory.rst to Simplified Chinese




在 2024/11/5 22:47, Jonathan Corbet 写道:
> Yanteng Si <si.yanteng@...ux.dev> writes:
>
>> 在 2024/11/5 03:27, Jonathan Corbet 写道:
>>> OK, I have applied this patch.  A couple of comments for future reference:
>>>
>>> <xu.xin16@....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")
> "Update to commit xxx" suggests that the current patch is somehow
> changing that commit.  "Update the translation through commit xxxx"
> would be a bit clearer in that regard.  I think it's better to stay with
> something resembling plain language rather than adding a new pseudo-tag
> that outsiders won't understand.
Approve!

Thanks,
Yanteng
>
> Thanks,
>
> jon
>
>