From: Akira Yokosawa <akiyks@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>, kurita <akito5623@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH] docs: ja_JP: Update SubmittingPatches for 'Fixes:' tag
Date: Fri, 5 Sep 2025 09:58:06 +0900 [thread overview]
Message-ID: <2955d7de-71a8-4767-914d-23e8d9f63971@gmail.com> (raw)
In-Reply-To: <878qiunyhu.fsf@trenco.lwn.net>
On Thu, 04 Sep 2025 07:22:37 -0600, Jonathan Corbet wrote:
> kurita <akito5623@gmail.com> writes:
>
>> The Japanese translation of SubmittingPatches is based on an old
>> kernel version (2.6.39) and is missing several new sections.
>>
>> This patch adds the missing description for the 'Fixes:' tag to
>> bring the document more in line with the current English original
>> (Documentation/process/submitting-patches.rst).
>>
>> Signed-off-by:Akiyoshi kurita <akito5623@gmail.com>
>> ---
>> Documentation/translations/ja_JP/SubmittingPatches | 4 ++++
>> 1 file changed, 4 insertions(+)
>
> So I only saw this because of Akira's response; something in how you are
> sending your mail drives SpamAssassin nuts.
It didn't make my Gmail's inbox nor spam folder either.
I only spotted it at the lore archive.
Akiyoshi, I see you have submitted other two versions of this patch already,
but both of them failed to make my inbox.
Your email message at the lore archive has these in its header:
ARC-Authentication-Results:i=2; smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=gmail.com; spf=none smtp.mailfrom=www.redadmin.org; arc=pass smtp.client-ip=49.212.207.181
Authentication-Results: smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=gmail.com
Authentication-Results: smtp.subspace.kernel.org; spf=none smtp.mailfrom=www.redadmin.org
The mail-list is probably generous and accepted it.
But Gmail is getting very strict these days.
I'm not going to review your patches until you fix whatever issue
on your (or your ISP?) side.
>
> Thank you for working to improve our documentation!
>
> In addition to everything Akira said, I must express a bit of worry
> about updating this document piecemeal in this way. Backporting
> specific pieces in this way will yield a result that is not a
> translation of anything - it is a new creation that never existed in the
> original form.
>
> It sure would be nicer (says the guy who has no ability to do that work)
> to bring the translation as a whole current.
Jon, of course that's the ultimate goal.
And that was exactly I did in commit 991dabb24232 ("docs/ja_JP: Convert
SubmitChecklist into reST with belated updates").
I did it because the original check-list has only 137 lines and its
direct translation would have ended up in odd looking one from Japanese
speaker's POV.
Thanks,
Akira
>
> I'll accept pieces with acks from people who can properly judge them,
> but I would prefer to just have a current translation.
>
> Thanks,
>
> jon
prev parent reply other threads:[~2025-09-05 0:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-03 11:35 [PATCH] docs: ja_JP: Update SubmittingPatches for 'Fixes:' tag kurita
2025-09-04 10:23 ` Akira Yokosawa
2025-09-04 13:22 ` Jonathan Corbet
2025-09-05 0:58 ` 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=2955d7de-71a8-4767-914d-23e8d9f63971@gmail.com \
--to=akiyks@gmail.com \
--cc=akito5623@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