From: Akira Yokosawa <akiyks@gmail.com>
To: Akiyoshi Kurita <weibu@redadmin.org>, corbet@lwn.net
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
Akira Yokosawa <akiyks@gmail.com>
Subject: Re: [PATCH] docs: ja_JP: process: translate second half of 'Describe your changes'
Date: Mon, 23 Mar 2026 17:11:51 +0900 [thread overview]
Message-ID: <68e16682-aba3-4e10-8776-1c04c55b7ddc@gmail.com> (raw)
In-Reply-To: <20260309105015.309116-1-weibu@redadmin.org>
Hi,
Sorry for the late response.
On Mon, 9 Mar 2026 19:50:15 +0900, Akiyoshi Kurita wrote:
> Translate the remaining part of the "Describe your changes" section in
> Documentation/translations/ja_JP/process/submitting-patches.rst.
>
> Follow review comments on wording and line wrapping, and cover guidance
> on self-contained patch descriptions, imperative mood, commit
> references, and Link:/Closes:/Fixes: tags.
>
> Signed-off-by: Akiyoshi Kurita <weibu@redadmin.org>
Acked-by: Akira Yokosawa <akiyks@gmail.com>
I have noticed a couple of minor translation issues in this patch,
but I'd rather submit a patch on top of this, rather than comment on
those issues in English.
I guess I can prepare a follow-up patch within a week.
By the way, now I see why Kurita-san is wrapping lines at 30 wide-chars
or so. I guess they are broken that way so that each line corresponds
to that in the English text. That makes sense.
Thanks, Akira
> ---
> .../ja_JP/process/submitting-patches.rst | 84 +++++++++++++++++++
> 1 file changed, 84 insertions(+)
>
[...]
next prev parent reply other threads:[~2026-03-23 8:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 10:50 [PATCH] docs: ja_JP: process: translate second half of 'Describe your changes' Akiyoshi Kurita
2026-03-23 8:11 ` Akira Yokosawa [this message]
2026-03-23 8:29 ` weibu
2026-03-25 19:46 ` 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=68e16682-aba3-4e10-8776-1c04c55b7ddc@gmail.com \
--to=akiyks@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=weibu@redadmin.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