From: Akira Yokosawa <akiyks@gmail.com>
To: Akiyoshi Kurita <weibu@redadmin.org>, linux-doc@vger.kernel.org
Cc: corbet@lwn.net, Akira Yokosawa <akiyks@gmail.com>
Subject: Re: [PATCH v5] docs/ja_JP: translate submitting-patches.rst (sign-off)
Date: Mon, 20 Jul 2026 16:20:21 +0900 [thread overview]
Message-ID: <7384a9ff-64cd-4772-990b-92aa5306751d@gmail.com> (raw)
In-Reply-To: <20260719181934.213142-1-weibu@redadmin.org>
On Mon, 20 Jul 2026 03:19:34 +0900, Akiyoshi Kurita wrote:
> Translate the "Include PATCH in the subject" and "Sign your work -
> the Developer's Certificate of Origin" sections into Japanese.
>
> Keep the DCO text in English as the original certificate text, and add
> a Japanese note that the sign-off refers to the English DCO text.
>
> Use a reStructuredText note directive to make it clear that the note is
> specific to the Japanese translation.
>
> Signed-off-by: Akiyoshi Kurita <weibu@redadmin.org>
> ---
> Changes in v5:
>
> Rebase on docs-next.
> Remove an extra blank line under the Signed-off-by line.
In the rebase, you have introduced this warning in "git am <this patch>":
.git/rebase-apply/patch:117: new blank line at EOF.
+
warning: 1 line adds whitespace errors.
See below.
>
> Changes in v4:
>
> Use a reStructuredText note directive to clarify that the explanation
> is specific to the Japanese translation.
[...]
> +作者の SoB に続く追加の SoB(``Signed-off-by:``)は、パッチの開発には
> +関与せず、その取り扱いや転送を行った人によるものです。SoB の連鎖は、
> +パッチがメンテナーを経て最終的に Linus へ届いた実際の経路を反映する
> +必要があります。最初の SoB は、単独の主要作者であることを示します。
> +
^^^ Here is the "new blank line at EOF".
> --
> 2.52.0
Please fix. You don't need to hurry.
Thanks, Akira
prev parent reply other threads:[~2026-07-20 7:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-19 18:19 [PATCH v5] docs/ja_JP: translate submitting-patches.rst (sign-off) Akiyoshi Kurita
2026-07-20 7:20 ` Akira Yokosawa [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=7384a9ff-64cd-4772-990b-92aa5306751d@gmail.com \
--to=akiyks@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@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