From: Akira Yokosawa <akiyks@gmail.com>
To: Akiyoshi Kurita <weibu@redadmin.org>, linux-doc@vger.kernel.org
Cc: corbet@lwn.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] docs: ja_JP: SubmittingPatches: describe the 'Fixes:' tag (12-char SHA-1 + pretty example)
Date: Tue, 9 Sep 2025 19:30:24 +0900 [thread overview]
Message-ID: <3af7a4d0-3587-4374-8087-4ad037e8c5f1@gmail.com> (raw)
In-Reply-To: <20250909022502.119560-1-weibu@redadmin.org>
On Tue, 9 Sep 2025 11:25:02 +0900, Akiyoshi Kurita wrote:
> Add a Japanese section describing the Fixes: tag, use a consistent
> 12-character SHA-1 in the example, and include the pretty-format
> snippet to generate a Fixes: line with git log/show.
> No functional changes.
>
> Signed-off-by: Akiyoshi Kurita <weibu@redadmin.org>
>
> ---
> v4:
> - Fix unnatural Japanese wording in the new Fixes: section for clarity.
> - No content change, only Japanese expression improved.
> - v4 fully replaces v3 (not incremental).
Sorry, but this is wrong. I needed to apply v4 on top of v3.
It is contributor's responsibility to make reviewers life easier,
Please be careful.
I think you need to understand Linux kernel's patch submission
conventions before starting sending patches.
Of course, submitting-patches.rst (or ja_JP's SubmittingPatches) should
be a good starting point for learning the process.
Probably, it would be better for you to send your WIP patches privately
(meaning without CCs) to me. Not necessarily in English.
Regards,
Akira
next prev parent reply other threads:[~2025-09-09 10:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 2:25 Akiyoshi Kurita
2025-09-09 10:30 ` Akira Yokosawa [this message]
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
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=3af7a4d0-3587-4374-8087-4ad037e8c5f1@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
all inboxes | Powered by JetHome®