From: Fu Wei <wefu@redhat.com>
To: Will Deacon <will.deacon@arm.com>
Cc: harryxiyou@gmail.com, corbet@lwn.net,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@zh-kernel.org, ard.biesheuvel@linaro.org,
catalin.marinas@arm.com
Subject: Re: [PATCH] Documentation:Update Documentation/zh_CN/arm64/booting.txt
Date: Thu, 28 Apr 2016 21:56:03 +0800 [thread overview]
Message-ID: <57221673.7010008@redhat.com> (raw)
In-Reply-To: <20160421164227.GN929@arm.com>
Hi Will
On 04/22/2016 12:42 AM, Will Deacon wrote:
> On Thu, Apr 21, 2016 at 09:45:40PM +0800, wefu@redhat.com wrote:
>> From: Fu Wei <wefu@redhat.com>
>>
>> This is a update of Chinese documentation: Documentation/zh_CN/arm64/booting.txt
>>
>> It is based on the modifications of Documentation/arm64/booting.txt in submission:
>> "a7f8de16".
>>
>> Signed-off-by: Fu Wei <wefu@redhat.com>
>> ---
>> Documentation/zh_CN/arm64/booting.txt | 20 ++++++++++++--------
>> 1 file changed, 12 insertions(+), 8 deletions(-)
>>
>> diff --git a/Documentation/zh_CN/arm64/booting.txt b/Documentation/zh_CN/arm64/booting.txt
>> index 1145bf8..c1dd968 100644
>> --- a/Documentation/zh_CN/arm64/booting.txt
>> +++ b/Documentation/zh_CN/arm64/booting.txt
>> @@ -8,7 +8,7 @@ or if there is a problem with the translation.
>>
>> M: Will Deacon <will.deacon@arm.com>
>> zh_CN: Fu Wei <wefu@redhat.com>
>> -C: 1926e54f115725a9248d0c4c65c22acaf94de4c4
>> +C: 55f058e7574c3615dea4615573a19bdb258696c6
>
> Just curious, but what are these SHAs supposed to represent? Neither of
> them looks particularly relevant to me.
Sorry for late response.
This is the checkout point when I translated the documentation.
I learn it from "MAINTAINERS", I would like to upstream my script patch
to keep track of the Documentation status. It can tell me
(1)which English doc is updated since I submitted the translation.
(2)which doc haven't been translated(a list)
M: original doc Maintainer(Maybe I should use "En" ro "E" for English)?
zh_CN: Chinese doc maintainer
C: Commit number or Checkout point
And my plan is that the patch can also be used in other languages, like
"ja_JP" and "ko_KR". I hope that can help or encourage more and more
people to do the doc translation work. And that can help people using
another language to learn and enjoy the kernel development more easily.
>
> Will
>
next prev parent reply other threads:[~2016-04-28 13:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-21 13:45 [PATCH] Documentation:Update Documentation/zh_CN/arm64/booting.txt wefu
2016-04-21 16:42 ` Will Deacon
2016-04-28 13:16 ` Jonathan Corbet
2016-04-28 14:00 ` Fu Wei
2016-04-28 13:56 ` Fu Wei [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-02-16 8:41 wefu
2016-02-16 8:51 ` Weiwei Jia
2016-02-16 10:10 ` Will Deacon
2016-02-16 12:48 ` Jonathan Corbet
2016-02-17 21:07 ` Jonathan Corbet
[not found] <=wefu@redhat.com>
2015-03-24 9:37 ` wefu
2015-03-24 9:42 ` harryxiyou
2015-03-26 17:14 ` Jonathan Corbet
2014-01-28 12:28 [PATCH]Documentation:Update Documentation/zh_CN/arm64/booting.txt Fu Wei
2014-01-28 13:38 ` jiaweiwei
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=57221673.7010008@redhat.com \
--to=wefu@redhat.com \
--cc=ard.biesheuvel@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=harryxiyou@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kernel@zh-kernel.org \
--cc=will.deacon@arm.com \
/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).