From: Akira Yokosawa <akiyks@gmail.com>
To: Tsugikazu Shibata <shibata@linuxfoundation.org>,
Kosuke Fujimoto <fujimotokosuke0@gmail.com>
Cc: corbet@lwn.net, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, Akira Yokosawa <akiyks@gmail.com>
Subject: Re: [PATCH v2] docs/ja_JP/howto: Don't mention specific kernel versions
Date: Thu, 28 Apr 2022 20:47:30 +0900 [thread overview]
Message-ID: <a332cd81-c234-7bff-ac2b-f19a4368210a@gmail.com> (raw)
In-Reply-To: <CAO+cJp0adp9W22zBbOnUvaLxa2fbsTky431NE_K+MbwyOLpZYQ@mail.gmail.com>
On Thu, 28 Apr 2022 17:40:27 +0900,
Tsugikazu Shibata wrote:
> First of all, Thanks to Fujimoto-san and Yokosawa-san for waking me up.
> Now I get back to here by new email address.
Welcome back, Shibata-san!
>
> I have a few comments as below:
>
> On Sun, Apr 24, 2022 at 9:28 PM Kosuke Fujimoto
> <fujimotokosuke0@gmail.com> wrote:
>>
>> This change is based on commit d2b008f134b7
>> ("Documentation/process/howto: Update for 4.x -> 5.x versioning").
>>
>> Replace "4.x kernel version" with generic term such as "mainline tree"
>>
>> Signed-off-by: Kosuke Fujimoto <fujimotokosuke0@gmail.com>
>> Reviewed-by: Akira Yokosawa <akiyks@gmail.com>
>> Cc: Jonathan Corbet <corbet@lwn.net>
>> Cc: Tsugikazu Shibata <shibata@linuxfoundation.org>
>> Cc: Akira Yokosawa <akiyks@gmail.com>
>> Cc: linux-doc@vger.kernel.org
>> ---
>> V2: Reformatted commit log message
>> ---
>> Documentation/translations/ja_JP/howto.rst | 43 ++++++++++------------
>> 1 file changed, 20 insertions(+), 23 deletions(-)
>>
>> diff --git a/Documentation/translations/ja_JP/howto.rst b/Documentation/translations/ja_JP/howto.rst
>> index d667f9d8a02a..9b711932ae6d 100644
>> --- a/Documentation/translations/ja_JP/howto.rst
>> +++ b/Documentation/translations/ja_JP/howto.rst
[...]
>> -4.x.y -stable カーネルツリー
>> -~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> +メジャー番号をまたぐ数本の安定版ツリー
>> +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>
>> バージョン番号が3つの数字に分かれているカーネルは -stable カーネルです。
>> -これには、4.x カーネルで見つかったセキュリティ問題や重大な後戻りに対す
>> -る比較的小さい重要な修正が含まれます。
>> +これには最初の2つの数字に対応した、メインラインリリースで見つかったセキュリティ問題や
>
> Above line comes from:
> ...security problems or significant regressions discovered in a given
> major mainline release,
> with the first 2-part of version number are the same correspondingly.
>
> It may better to be:
> これには最初の2つのバージョン番号の数字に対応した、メインラインリリースで見つかったセキュリティ問題や
This looks more faithful.
>
>> +重大な後戻りに対する比較的小さい重要な修正が含まれます。
>>
>> これは、開発/実験的バージョンのテストに協力することに興味が無く、最新
>> の安定したカーネルを使いたいユーザに推奨するブランチです。
>>
>> -もし、4.x.y カーネルが存在しない場合には、番号が一番大きい 4.x が最新
>> -の安定版カーネルです。
>> -
>> -4.x.y は "stable" チーム <stable@vger.kernel.org> でメンテされており、
>> +安定版カーネル は "stable" チーム <stable@vger.kernel.org> でメンテされており、
>
> This line comes from:
> Stable trees are maintained by the "stable" team <stable@vger.kernel.org>, ...
>
> So, It may also better to be:
> 安定版ツリーは"stable" チーム <stable@vger.kernel.org> でメンテされており、
Ditto.
Fujimoto-san, please keep my Reviewed-by: tag in the next spin.
Thanks, Akira
>
> For other parts it looks good to me. I hope you will fix and submit
> your patch again.
> Thank you for your patch.
>
> Tsugikazu Shibata
prev parent reply other threads:[~2022-04-28 11:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-24 12:27 Kosuke Fujimoto
2022-04-28 8:40 ` Tsugikazu Shibata
2022-04-28 11:47 ` 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=a332cd81-c234-7bff-ac2b-f19a4368210a@gmail.com \
--to=akiyks@gmail.com \
--cc=corbet@lwn.net \
--cc=fujimotokosuke0@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shibata@linuxfoundation.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®