public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: weibu@redadmin.org
To: Akira Yokosawa <akiyks@gmail.com>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, corbet@lwn.net
Subject: Re: [PATCH v2] docs: ja_JP: SubmittingPatches: document the 'Fixes:' tag (+example)
Date: Sat, 06 Sep 2025 00:36:38 +0900	[thread overview]
Message-ID: <c5a767e4d064cee8092b79ebc30e9cb0@redadmin.org> (raw)
In-Reply-To: <cd17b8f5-b5f2-4d9a-87af-04ecb2a235ba@gmail.com>

Hi Akira-san,

Thank you very much for your review and detailed feedback.

I will update the Fixes: example to use a consistent 12-character SHA-1 
hash.

I will also move the Link: line under the --- separator, as per 
convention.

To clarify: v2 was intended as a full replacement of v1, not something 
to be applied on top of it. I’ll make that explicit in the changelog 
section for v3.

I’ll prepare and send a v3 patch early next week with these corrections.

Thanks again for your guidance, and have a good weekend.

Best regards,
Akiyoshi Kurita

2025-09-06 00:14 に Akira Yokosawa さんは書きました:
> Hi,
> 
> On Fri,  5 Sep 2025 20:14:03 +0900, Akiyoshi Kurita wrote:
>> Sync the ja_JP translation with parts of:
>>   - 8401aa1f5997 ("Documentation/SubmittingPatches: describe the 
>> Fixes: tag")
>>   - 5b5bbb8cc51be ("docs: process: Add an example for creating a fixes 
>> tag")
> 
> Consistent SHA-1 hash length would look nicer.
> 
>> 
>> Link: 
>> https://lore.kernel.org/all/20250905032729.2284883-1-weibu@redadmin.org/
> 
> This link to v1 needs to be under the "---" below.
> 
> Wait, do you mean this patch is supposed to be applied on top of v1?
> 
>> Signed-off-by: Akiyoshi Kurita <weibu@redadmin.org>
>> 
>> ---
>> v2:
>>   - Add explanatory paragraphs from 8401aa1f5997 (purpose + stable 
>> note)
>>   - Keep example and pretty-format from 5b5bbb8cc51be
>>  Documentation/translations/ja_JP/SubmittingPatches | 12 ++++++++++++
>>  1 file changed, 12 insertions(+)
>> 
> 
> I think I need to be more clear on what I am expecting.
> I'll send a follow-up comment early next week.
> 
> Have a nice weekend!
> 
> Thanks,
> Akira

      reply	other threads:[~2025-09-05 15:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-05  3:27 [PATCH] docs: ja_JP: add guidance for the Fixes: tag in SubmittingPatches Akiyoshi Kurita
2025-09-05  9:48 ` Akira Yokosawa
2025-09-05  9:59   ` weibu
2025-09-05 11:14 ` [PATCH v2] docs: ja_JP: SubmittingPatches: document the 'Fixes:' tag (+example) Akiyoshi Kurita
2025-09-05 15:14   ` Akira Yokosawa
2025-09-05 15:36     ` weibu [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=c5a767e4d064cee8092b79ebc30e9cb0@redadmin.org \
    --to=weibu@redadmin.org \
    --cc=akiyks@gmail.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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