public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Akira Yokosawa <akiyks@gmail.com>
To: Akiyoshi Kurita <weibu@redadmin.org>
Cc: linux-kernel@vger.kernel.org, corbet@lwn.net, linux-doc@vger.kernel.org
Subject: Re: [PATCH v3] docs/ja_JP: translate more of submitting-patches.rst
Date: Sat, 2 May 2026 14:25:25 +0900	[thread overview]
Message-ID: <6af83511-4e0a-4f09-a16b-6812d25f9b4d@gmail.com> (raw)
In-Reply-To: <20260501191114.939418-1-weibu@redadmin.org>

Hi,

On 2 May 2026 04:11:14 +0900, Akiyoshi Kurita wrote:
> Translate the "Separate your changes", "Style-check your changes",
> and "Select the recipients for your patch" sections in
> Documentation/translations/ja_JP/process/submitting-patches.rst.
> 
> Keep the wording close to the English text and wrap lines to match
> the style used in the surrounding Japanese translation.
> 
> Signed-off-by: Akiyoshi Kurita <weibu@redadmin.org>
> ---
> v3:
> - Use a file-local cross-reference to the translated "変更を分割する" section
> - Keep the TODO for the untranslated "The canonical patch format" section
> - Drop the obsolete TODO for "Separate your changes"
> - Rewrap the latter part more consistently
> 
>  .../ja_JP/process/submitting-patches.rst      | 123 +++++++++++++++++-
>  1 file changed, 118 insertions(+), 5 deletions(-)

This does not apply on docs-next.

> 
> diff --git a/Documentation/translations/ja_JP/process/submitting-patches.rst b/Documentation/translations/ja_JP/process/submitting-patches.rst
> index 91bd79a0e9dc..8f85d2cfde71 100644

At docs-next, .../ja_JP/process/submitting-patches.rst has index 9d63220abd15.

Your patch should start with:

index 9d63220abd15..xxxxxxxxxxxx 100644

Please rebase and resend.

Thanks, Akira

[...]


      reply	other threads:[~2026-05-02  5:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-01 19:11 [PATCH v3] docs/ja_JP: translate more of submitting-patches.rst Akiyoshi Kurita
2026-05-02  5:25 ` 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=6af83511-4e0a-4f09-a16b-6812d25f9b4d@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