mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Akiyoshi Kurita <weibu@redadmin.org>, linux-doc@vger.kernel.org
Cc: akiyks@gmail.com, linux-kernel@vger.kernel.org, weibu@redadmin.org
Subject: Re: [PATCH v5] docs: ja_JP: SubmittingPatches: describe the 'Fixes:' tag
Date: Tue, 14 Oct 2025 09:02:48 -0600	[thread overview]
Message-ID: <87jz0xbk6f.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20250924192426.2743495-1-weibu@redadmin.org>

Akiyoshi Kurita <weibu@redadmin.org> writes:

> Sync the ja_JP translation with the following upstream commits:
>
> commit 8401aa1f5997 ("Documentation/SubmittingPatches: describe the Fixes: tag")
> commit 19c3fe285cba ("docs: Explicitly state that the 'Fixes:' tag shouldn't split lines")
> commit 5b5bbb8cc51b ("docs: process: Add an example for creating a fixes tag")
> commit 6356f18f09dc ("Align git commit ID abbreviation guidelines and checks")
>
> The mix of plain text and reST markup for ``git bisect`` is intentional to
> align with the eventual reST conversion.
>
> Signed-off-by: Akiyoshi Kurita <weibu@redadmin.org>
> ---
> v5:
>  - whole rewrite
> ---
>  .../translations/ja_JP/SubmittingPatches      | 28 ++++++++++++++++++-
>  1 file changed, 27 insertions(+), 1 deletion(-)

Applied.

That said ... this is not an RST file, and won't be pulled into the docs
build.  I would *love* to see a patch that moves this file into its
proper location under .../process/ and brings it into the build.

Thanks,

jon

  parent reply	other threads:[~2025-10-14 15:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-09  2:25 [PATCH v4] docs: ja_JP: SubmittingPatches: describe the 'Fixes:' tag (12-char SHA-1 + pretty example) Akiyoshi Kurita
2025-09-09 10:30 ` Akira Yokosawa
2025-09-24 19:24 ` [PATCH v5] docs: ja_JP: SubmittingPatches: describe the 'Fixes:' tag Akiyoshi Kurita
2025-09-25 12:03   ` Akira Yokosawa
2025-10-14 15:02   ` Jonathan Corbet [this message]
2025-10-15 14:57     ` weibu

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=87jz0xbk6f.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=akiyks@gmail.com \
    --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

all inboxes | Powered by JetHome®