linux-kernel - Re: [PATCH v5] docs: ja_JP: SubmittingPatches: describe the 'Fixes:' tag

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <11158ff57b6b33b31a2d2fcb78842d25@redadmin.org>
Date: Wed, 15 Oct 2025 23:57:07 +0900
From: weibu@...admin.org
To: Jonathan Corbet <corbet@....net>
Cc: linux-doc@...r.kernel.org, akiyks@...il.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v5] docs: ja_JP: SubmittingPatches: describe the 'Fixes:'
 tag

Thanks, I’ll follow up by moving this under 
.../translations/ja_JP/process/, converting it to RST, and wiring it 
into the Sphinx toctree so it’s built.

2025-10-15 00:02 に Jonathan Corbet さんは書きました:
> Akiyoshi Kurita <weibu@...admin.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@...admin.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