From: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
To: Haowen Bai <baihaowen@meizu.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] docs/zh_CN: sync with original text Documentation/vm/page_owner.rst
Date: Mon, 25 Apr 2022 18:57:22 +0200 [thread overview]
Message-ID: <YmbS8ll0LP1Axrm5@latitude> (raw)
In-Reply-To: <1650871931-10015-2-git-send-email-baihaowen@meizu.com>
[-- Attachment #1: Type: text/plain, Size: 139 bytes --]
On Mon, Apr 25, 2022 at 03:32:10PM +0800, Haowen Bai wrote:
[...]
> +--curl 选项:
This should be --cull, not --curl.
Jonathan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-04-25 16:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-25 7:32 [PATCH 0/2] sync with original text Documentation/vm/page_owner.rst Haowen Bai
2022-04-25 7:32 ` [PATCH 1/2] docs/zh_CN: " Haowen Bai
2022-04-25 16:57 ` Jonathan Neuschäfer [this message]
2022-04-25 7:32 ` [PATCH 2/2] doc/vm/page_owner.rst: Fix table display confusion Haowen Bai
-- strict thread matches above, loose matches on Subject: below --
2022-04-26 7:07 [PATCH 0/2] sync with original text Documentation/vm/page_owner.rst Haowen Bai
2022-04-26 7:07 ` [PATCH 1/2] docs/zh_CN: " Haowen Bai
[not found] <1650956694-30699-1-git-send-email-baihaowen@meizu.com>
2022-04-26 7:04 ` Haowen Bai
2022-04-19 14:42 [PATCH V8] " yanteng si
2022-04-20 3:06 ` [PATCH 0/2] " Haowen Bai
2022-04-20 3:06 ` [PATCH 1/2] docs/zh_CN: " Haowen Bai
2022-04-23 10:27 ` Alex Shi
2022-04-24 2:56 ` baihaowen
2022-04-24 3:16 ` Alex Shi
2022-04-25 1:17 ` baihaowen
2022-04-25 3:19 ` yanteng si
2022-04-25 8:18 ` baihaowen
2022-04-26 6:57 ` yanteng si
2022-04-26 8:20 ` Alex Shi
2022-04-26 8:23 ` baihaowen
[not found] ` <3f93bb0d-5658-f269-f8cc-d0a964ffb68b@gmail.com>
2022-04-26 8:30 ` baihaowen
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=YmbS8ll0LP1Axrm5@latitude \
--to=j.neuschaefer@gmx.net \
--cc=baihaowen@meizu.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox