public inbox for docs@lists.yoctoproject.org
 help / color / mirror / Atom feed
From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: Takayasu Ito <ypa.takayasu.ito@gmail.com>
Cc: docs@lists.yoctoproject.org
Subject: Re: [docs] [PATCH] migration-guide: add release notes for 4.0.16
Date: Mon, 29 Jan 2024 16:07:12 +0100	[thread overview]
Message-ID: <5dfd6147-bde4-4727-ba21-6dc8780b129e@bootlin.com> (raw)
In-Reply-To: <497c3940-b6c3-4863-a4a8-e9b63eb7a483@gmail.com>

Hi Takayasu-San

Thanks for the review!

On 1/29/24 at 14:33, Takayasu Ito wrote:
> Hi Lee,
>
> I see that the Fixed and Security Fixes are listed in opposite places.


Ah right, the section titles are correct and well located, but their 
contents should be swapped.

>
> In the actual Security Fixes, cpio is listed above curl if it is 
> listed in ascending order.


Indeed, that would be nice to fix for consistency.

>
> In the actual Fixes section, "docs" and "documentation" are listed 
> differently for the same subject.
> I also need to be careful about the use of "manuals" and "documentation".


Right, I must confess I haven't paid too much attention to this so far, 
as nobody seemed to care.
Perhaps, we should enforce a "docs" prefix for all documentation 
contributions, and still mention the modified manual when only one 
manual is modified.

What do you think?

Anyway, I wouldn't rewrite the documentation commits we have so far as 
this is probably complicated, and as this has been happening for a long 
time.

Lee, do you have time for a quick V2? I can take care of it too...

Thanks again
Michael.

-- 
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



      reply	other threads:[~2024-01-29 15:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-29  5:57 [PATCH] migration-guide: add release notes for 4.0.16 chee.yang.lee
2024-01-29 13:33 ` [docs] " Takayasu Ito
2024-01-29 15:07   ` Michael Opdenacker [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=5dfd6147-bde4-4727-ba21-6dc8780b129e@bootlin.com \
    --to=michael.opdenacker@bootlin.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=ypa.takayasu.ito@gmail.com \
    /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