From: Jonathan Corbet <corbet@lwn.net>
To: Haoyang Liu <tttturtleruss@hust.edu.cn>,
Alex Shi <alexs@kernel.org>, Yanteng Si <siyanteng@loongson.cn>
Cc: hust-os-kernel-patches@googlegroups.com,
Haoyang Liu <tttturtleruss@hust.edu.cn>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] docs/zh_CN: Add dev-tools/kmemleak Chinese translation
Date: Wed, 10 Apr 2024 15:27:36 -0600 [thread overview]
Message-ID: <87zfu0sybb.fsf@meer.lwn.net> (raw)
In-Reply-To: <20240403052552.39292-1-tttturtleruss@hust.edu.cn>
Haoyang Liu <tttturtleruss@hust.edu.cn> writes:
> Translate dev-tools/kmemleak.rst into Chinese and add it into
> zh_CN/dev-tools/index.rst.
>
> Signed-off-by: Haoyang Liu <tttturtleruss@hust.edu.cn>
> ---
> v1 -> v2: Adjust line length and keep consistent with the original content
>
> .../translations/zh_CN/dev-tools/index.rst | 2 +-
> .../translations/zh_CN/dev-tools/kmemleak.rst | 229 ++++++++++++++++++
> 2 files changed, 230 insertions(+), 1 deletion(-)
> create mode 100644 Documentation/translations/zh_CN/dev-tools/kmemleak.rst
Applied, thanks.
Incidentally, I see you sent a v3 adding just the reviewed-by tag. If
you change a patch for other reasons, you should definitely add such
tags (assuming the change isn't one that requires re-review, of course),
but there is no need to send a new version just to be sure that the tag
is picked up - b4 is great for that.
jon
prev parent reply other threads:[~2024-04-10 21:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 5:25 [PATCH v2] docs/zh_CN: Add dev-tools/kmemleak Chinese translation Haoyang Liu
2024-04-06 3:49 ` Yanteng Si
2024-04-10 21:27 ` Jonathan Corbet [this message]
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=87zfu0sybb.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=alexs@kernel.org \
--cc=hust-os-kernel-patches@googlegroups.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=siyanteng@loongson.cn \
--cc=tttturtleruss@hust.edu.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