From: baihaowen <baihaowen@meizu.com>
To: yanteng si <siyanteng01@gmail.com>
Cc: Alex Shi <alexs@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
"Linux Doc Mailing List" <linux-doc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, Alex Shi <seakeel@gmail.com>,
Yanteng Si <siyanteng@loongson.cn>
Subject: Re: [PATCH 0/2] sync with original text Documentation/vm/page_owner.rst
Date: Fri, 22 Apr 2022 09:40:39 +0800 [thread overview]
Message-ID: <93467d50-8ffb-0fb7-cafb-60eb2dd44130@meizu.com> (raw)
In-Reply-To: <CAEensMxtk8zJPAM-u7hvYkaNTBrVdmhKA7YzVsKmTw0TcOE=Pw@mail.gmail.com>
在 4/21/22 8:26 PM, yanteng si 写道:
> Haowen Bai <baihaowen@meizu.com> 于2022年4月20日周三 11:07写道:
>> This patches series will sync the translation of zh_CN as below:
>>
>> Commit 8bd16bc0a081 ("tools/vm/page_owner_sort.c: support sorting blocks
>> by multiple keys") add sorting blocks by multiple keys usage
>> description.
>>
>> Commit 78a0b94f3829 ("tools/vm/page_owner_sort.c: support for multi-value
>> selection in single argument") add multi-value selection in single
>> argument usage description.
>>
>> Commit c89b3ad2dea2 ("doc/vm/page_owner.rst: remove content related to -c
>> option") remove -c option usage description.
>>
>> Commit 9c8a0a8e599f ("tools/vm/page_owner_sort.c: support for user-defined
>> culling rules") add user-defined culling rules usage description.
>>
>> Commit 8ea8613a616a ("tools/vm/page_owner_sort.c: support for selecting by
>> PID, TGID or task command name") add selecting by PID, TGID or task
>> command name usage description.
>>
>> Commit 194d52d771b8 ("tools/vm/page_owner_sort: support for sorting by
>> task command name") add sorting by task command name usage description.
>>
>> But the original text table which is made of tab will display all
>> by one line. so we make a standard table for STANDARD FORMAT SPECIFIERS
>> description. I fix it up togeter by this patches series.
>>
>>
>> Haowen Bai (2):
>> docs/zh_CN: sync with original text Documentation/vm/page_owner.rst
>> doc/vm/page_owner.rst: Fix table display confusion
> hi haowen,
>
> I'm not sure why, your different versions of the patch are in one
> thread and they look like this inside
> <https://lore.kernel.org/linux-doc/>:
>
> [PATCH V3] docs/zh_CN: sync with original text Documentation/vm/page_owner.rst
> 2022-04-20 12:46 UTC (22+ messages)
> ` [PATCH V4] "
> ` [PATCH V5] "
> ` [PATCH V6] "
> ` [PATCH V7] "
> ` [PATCH V8] "
> ` [PATCH 0/2] "
> ` [PATCH 1/2] docs/zh_CN: "
> ` [PATCH 2/2] doc/vm/page_owner.rst: Fix
> table display confusion
I always reply mail using below method:
git send-email \
--in-reply-to='CAEensMxtk8zJPAM-u7hvYkaNTBrVdmhKA7YzVsKmTw0TcOE=Pw@mail.gmail.com' \
--to=siyanteng01@gmail.com \
--cc=alexs@kernel.org \
--cc=baihaowen@meizu.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=seakeel@gmail.com \
--cc=siyanteng@loongson.cn \
--subject='Re: [PATCH 0/2] sync with original text Documentation/vm/page_owner.rst' \
/path/to/YOUR_REPLY
link previous
> This will make trouble for the maintainer,Usually, they should look like this:
>
> [PATCH 0/2] docs/zh_CN: add hmm and numa translation
> 2022-04-21 11:59 UTC (3+ messages)
> ` [PATCH 1/2] docs/zh_CN: add vm hmm translation
> ` [PATCH 2/2] docs/zh_CN: add vm numa translation
>
>
> Thanks,
> Yanteng
>
>> Documentation/translations/zh_CN/vm/page_owner.rst | 61 +++++++++++++++++++++-
>> Documentation/vm/page_owner.rst | 34 +++++++-----
>> 2 files changed, 80 insertions(+), 15 deletions(-)
>>
>> --
>> 2.7.4
>>
--
Haowen Bai
next prev parent reply other threads:[~2022-04-22 1:40 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-15 1:30 [PATCH V3] docs/zh_CN: sync with original text Documentation/vm/page_owner.rst 司延腾
2022-04-15 2:09 ` yanteng si
2022-04-18 1:58 ` yanteng si
2022-04-18 9:28 ` [PATCH V4] " Haowen Bai
2022-04-18 12:41 ` Alex Shi
2022-04-19 1:23 ` Haowen Bai
2022-04-19 1:46 ` yanteng si
2022-04-19 2:07 ` [PATCH V5] " Haowen Bai
2022-04-19 2:33 ` yanteng si
2022-04-19 3:24 ` baihaowen
2022-04-19 3:34 ` [PATCH V6] " Haowen Bai
2022-04-19 4:27 ` [PATCH V5] " Alex Shi
2022-04-19 5:49 ` [PATCH V7] " Haowen Bai
2022-04-19 7:34 ` [PATCH V8] " Haowen Bai
2022-04-19 14:42 ` 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
2022-04-20 3:06 ` [PATCH 2/2] doc/vm/page_owner.rst: Fix table display confusion Haowen Bai
2022-04-20 12:31 ` Bagas Sanjaya
2022-04-20 12:46 ` Jonathan Corbet
2022-04-24 3:38 ` Akira Yokosawa
2022-04-24 5:24 ` Jonathan Corbet
2022-04-26 8:39 ` Alex Shi
2022-04-21 12:26 ` [PATCH 0/2] sync with original text Documentation/vm/page_owner.rst yanteng si
2022-04-22 1:40 ` baihaowen [this message]
2022-04-22 2:35 ` Akira Yokosawa
2022-04-19 1:24 ` [PATCH V4] docs/zh_CN: " baihaowen
2022-04-18 9:29 ` [PATCH V3] " baihaowen
2022-04-25 7:32 [PATCH 0/2] " Haowen Bai
2022-04-26 7:07 Haowen Bai
2022-04-26 11:52 ` Jonathan Corbet
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=93467d50-8ffb-0fb7-cafb-60eb2dd44130@meizu.com \
--to=baihaowen@meizu.com \
--cc=alexs@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=seakeel@gmail.com \
--cc=siyanteng01@gmail.com \
--cc=siyanteng@loongson.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).