From: Fu Wei <wefu@redhat.com>
To: Jonathan Corbet <corbet@lwn.net>, Will Deacon <will.deacon@arm.com>
Cc: harryxiyou@gmail.com, 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 22:00:16 +0800 [thread overview]
Message-ID: <57221770.60501@redhat.com> (raw)
In-Reply-To: <20160428071620.1eda6c3d@lwn.net>
Hi Jonathan,
On 04/28/2016 09:16 PM, Jonathan Corbet wrote:
> On Thu, 21 Apr 2016 17:42:28 +0100
> Will Deacon <will.deacon@arm.com> wrote:
>
>>> -C: 1926e54f115725a9248d0c4c65c22acaf94de4c4
>>> +C: 55f058e7574c3615dea4615573a19bdb258696c6
>>
>> Just curious, but what are these SHAs supposed to represent? Neither of
>> them looks particularly relevant to me.
>
> I'm kind of assuming it's the head of the repo at the time the update was
> done.
yes, you are right. :-)
next time, I just need to do
"git diff 55f058e7574c3615dea4615573a19bdb258696c6..HEAD <English doc> >
doc.patch" to see the difference :-)
>
> I've applied the patch to the docs tree, anyway.
Great thanks for your help! :-)
>
> Thanks,
>
> jon
>
next prev parent reply other threads:[~2016-04-28 14:00 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 [this message]
2016-04-28 13:56 ` Fu Wei
-- 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=57221770.60501@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).