From: Akira Yokosawa <akiyks@gmail.com>
To: Tsugikazu Shibata <shibata@linuxfoundation.org>,
Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Kosuke Fujimoto <fujimotokosuke0@gmail.com>,
Akira Yokosawa <akiyks@gmail.com>
Subject: Re: [PATCH] docs/ja_JP/howto: Update for v6.1
Date: Tue, 8 Nov 2022 00:00:56 +0900 [thread overview]
Message-ID: <6e64768e-d245-dbd5-7258-2b1b72fab5ee@gmail.com> (raw)
In-Reply-To: <CAO+cJp20skpBaWwG+yoRJtwv+L98HYfonZxc_qfEZL2JJp_9EA@mail.gmail.com>
On Fri, 4 Nov 2022 21:01:28 +0900, Tsugikazu Shibata wrote:
> On Sun, Oct 30, 2022 at 8:52 PM Akira Yokosawa <akiyks@gmail.com> wrote:
>>
>> Reflect changes made in commits listed below:
>>
>> 388f9b20f98d ("Documentation/process/howto: Only send regression fixes after -rc1").
>> bc0ef4a7e4c3 ("Doc: Delete reference to the kernel-mentors mailing list")
>> bcd3cf0855c5 ("Doc: Remove outdated info about bugzilla mailing lists")
>> dad051395413 ("Doc: add a missing cross-reference")
>> 9799445af124 ("Doc: tidy up TOCs and refs to license-rules.rst")
>> fb0e0ffe7fc8 ("Documentation: bring process docs up to date")
>> e7b4311ebcac ("Replace HTTP links with HTTPS ones: Documentation/process")
>> f1eebe92c265 ("Documentation/HOWTO: adjust external link references")
>> da514157c4f0 ("docs: make reporting-bugs.rst obsolete")
>> cf6d6fc27936 ("docs: process/howto.rst: make sections on bug reporting match practice")
>>
>> Co-developed-by: Kosuke Fujimoto <fujimotokosuke0@gmail.com>
>> Signed-off-by: Kosuke Fujimoto <fujimotokosuke0@gmail.com>
>> Signed-off-by: Akira Yokosawa <akiyks@gmail.com>
>> Cc: Tsugikazu Shibata <shibata@linuxfoundation.org>
>> ---
>> Brief history of the change:
>>
>> I (Akira) asked Kosuke of updating ja_JP/howto.rst after the merge of
>> his earlier contributions:
>> e0bd6f14c28f ("docs/ja_JP/index: update section title in Japanese")
>> 6548e96edb50 ("docs/trans/ja_JP/howto: Don't mention specific kernel versions")
>>
>> Kosuke made his WIP commits public at:
>> https://github.com/KosukeFujimoto/linux/tree/WIP-docs-ja-jp-howto
>>
>> He moved over to other responsibilities soon after and could not make
>> them ready for submission. Seeing almost half a year had passed without
>> any activity, I took over and assembled those small changes into a single
>> patch.
>>
>> I picked Kosuke's S-o-b from his github commits.
>> As I also improved some of translations along the way, I assigned myself
>> as the author and added Kosuke's co-developed-by tag.
>>
>> Shibata-san, hopefully can you review this update?
>>
>> Jon, I'll ask you when I feel like this one is ready to be applied.
>>
>> Thanks, Akira
>> --
>> Documentation/translations/ja_JP/howto.rst | 66 ++++++++++------------
>> 1 file changed, 31 insertions(+), 35 deletions(-)
>>
[...]
>
> Thank you for the patches and all the patches look good to me.
> Acked-by: Tsugikazu Shibata <shibata@linuxfoundation.org>
Thank you Shitata-san for taking the time to review.
Jon, looks like this is ready for v6.2.
Thanks, Akira
>
> Tsugikazu Shibata
next prev parent reply other threads:[~2022-11-07 15:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-30 11:52 [PATCH] docs/ja_JP/howto: Update for v6.1 Akira Yokosawa
2022-11-04 12:01 ` Tsugikazu Shibata
2022-11-07 15:00 ` Akira Yokosawa [this message]
2022-11-09 20:31 ` Jonathan Corbet
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=6e64768e-d245-dbd5-7258-2b1b72fab5ee@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