Linux Documentation
 help / color / mirror / Atom feed
From: Kosuke Fujimoto <fujimotokosuke0@gmail.com>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: Tsugikazu Shibata <shibata@linuxfoundation.org>,
	Jonathan Corbet <corbet@lwn.net>,
	Shuah Khan <skhan@linuxfoundation.org>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] docs/trans/ja_JP/howto: Don't mention specific kernel versions
Date: Sat, 30 Apr 2022 15:26:41 +0900	[thread overview]
Message-ID: <A7E94B97-84F6-4BDB-B5C3-33AADE91D877@gmail.com> (raw)
In-Reply-To: <475af784-ae64-1a8c-6e81-cf64cf3079b8@gmail.com>



> On Apr 30, 2022, at 15:01, Akira Yokosawa <akiyks@gmail.com> wrote:
> 
> On Sat, 30 Apr 2022 14:44:33 +0900,
> Tsugikazu Shibata wrote:
>> Hello Fujimoto-san,
>> 
>> Thanks for the patch.
>> Unfortunately, I found one more issue..
>> 
>> On Sat, Apr 30, 2022 at 8:00 AM 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>
>>> ---
>>> V2: Reformatted commit log messagae (Yokosawa-san)
>>> V3: Updated some expressions (Shibata-san)
>>> - added "version number" in mainline tree section
>>> - updated from "stable kernel" to "stable tree"
>>> V4: Added reviewed by tag and removed extra characters (Yokosawa-san)
>>> ---
>>> Documentation/translations/ja_JP/howto.rst | 44 +++++++++++-----------
>>> 1 file changed, 21 insertions(+), 23 deletions(-)
>>> 
>>> diff --git a/Documentation/translations/ja_JP/howto.rst b/Documentation/translations/ja_JP/howto.rst
>>> index d667f9d8a02a..deac41eb038a 100644
>>> --- a/Documentation/translations/ja_JP/howto.rst
>>> +++ b/Documentation/translations/ja_JP/howto.rst
> [...]
>>> 
>>> -このやり方によって、-next カーネルは次のマージ機会でどんなものがメイン
>>> -ラインカーネルにマージされるか、おおまかなの展望を提供します。-next カー
>>> -ネルの実行テストを行う冒険好きなテスターは大いに歓迎されます。
>>> +このやり方によって、linux-next は次のマージ機会でどんなものがメイン
>>> +ラインにマージされるか、おおまかなの展望を提供します。
>> 
>> This would be:
>> ラインにマージされるか、おおまかな展望を提供します。
> 
> Good eyes!
> I'm beginning to think I can't be a good reviewer...  :-/
> 
> Fujimoto-san, please keep my Reviewed-by: tag in v5.
> As Shibata-san might catch something else, v5 can wait for a day
> or so, I guess.
> 
>        Thanks, Akira
> 

Hi Shibata-san, 

Thank you for pointing that out. 
I will fix it and submit tomorrow as Yokosawa-san suggested.

Thanks,
Kosuke

>> 
>> Thank you for fixing this document.
>> 
>> Tsugikazu Shibata


      reply	other threads:[~2022-04-30  6:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-29 23:00 [PATCH v4] docs/trans/ja_JP/howto: Don't mention specific kernel versions Kosuke Fujimoto
2022-04-30  5:44 ` Tsugikazu Shibata
2022-04-30  6:01   ` Akira Yokosawa
2022-04-30  6:26     ` Kosuke Fujimoto [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=A7E94B97-84F6-4BDB-B5C3-33AADE91D877@gmail.com \
    --to=fujimotokosuke0@gmail.com \
    --cc=akiyks@gmail.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shibata@linuxfoundation.org \
    --cc=skhan@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