public inbox for docs@lists.yoctoproject.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Paul Eggleton <bluelightning@bluelightning.org>,
	 docs@lists.yoctoproject.org
Cc: michael.opdenacker@bootlin.com
Subject: Re: [docs] [PATCH 00/17] Documentation updates for 4.2
Date: Sat, 22 Apr 2023 11:01:36 +0100	[thread overview]
Message-ID: <f427391295df1ee31f77de7ffaa7cac103e66e72.camel@linuxfoundation.org> (raw)
In-Reply-To: <cover.1682133339.git.bluelightning@bluelightning.org>

On Sat, 2023-04-22 at 15:19 +1200, Paul Eggleton wrote:
> Release notes, migration guide and additional manual updates for the
> imminent 4.2 release.
> 
> As usual I found a bunch of things that were undocumented that I either
> needed to link to or that I felt should be completed, those are included
> in this series. There is also a dependency on the BitBake User Manual
> changes I just sent.
> 
> Please let me know if I missed or messed up anything :) Thanks.

Thanks Paul, you do have an eye for this and do a great job, it is very
much appreciated.

Things looked good from my perspective and improve things. We're about
to rebuild the release due to a kernel issue so I decided to pull these
into the rebuild. If there are any issues Michael spots when he is
back, we can improve as needed with further patches.

Cheers,

Richard






      parent reply	other threads:[~2023-04-22 10:01 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-22  3:19 [PATCH 00/17] Documentation updates for 4.2 Paul Eggleton
2023-04-22  3:19 ` [PATCH 01/17] ref-manual: add new SDK_ZIP_OPTIONS variable Paul Eggleton
2023-04-22  3:19 ` [PATCH 02/17] ref-manual: Add new RUST_CHANNEL variable Paul Eggleton
2023-04-22  3:19 ` [PATCH 03/17] ref-manual: update for IMAGE_MACHINE_SUFFIX addition Paul Eggleton
2023-04-22  3:19 ` [PATCH 04/17] Remove references to INC_PR Paul Eggleton
2023-04-22  3:19 ` [PATCH 05/17] ref-manual: add BB_CACHEDIR Paul Eggleton
2023-04-22  3:19 ` [PATCH 06/17] Add coverage of addpylib directive Paul Eggleton
2023-04-22  3:19 ` [PATCH 07/17] Remove references to package_tar class Paul Eggleton
2023-04-22  3:19 ` [PATCH 08/17] ref-manual: add missing QA checks from previous releases Paul Eggleton
2023-04-22  3:19 ` [PATCH 09/17] ref-manual: document new patch-status-* QA checks Paul Eggleton
2023-04-22  3:19 ` [PATCH 10/17] ref-manual: add FIT_CONF_DEFAULT_DTB Paul Eggleton
2023-04-22  3:19 ` [PATCH 11/17] ref-manual: add section link also to buildtools-extended entry Paul Eggleton
2023-04-22  3:19 ` [PATCH 12/17] ref-manual: add SDK_ARCHIVE_TYPE Paul Eggleton
2023-04-22  3:19 ` [PATCH 13/17] ref-manual: move Initramfs entry from variables to terms Paul Eggleton
2023-04-22  3:19 ` [PATCH 14/17] Document INIT_MANAGER Paul Eggleton
2023-04-22  3:19 ` [PATCH 15/17] migration-guides: extend migration guide for 4.2 Paul Eggleton
2023-04-22  3:19 ` [PATCH 16/17] release-notes-4.1: fix some CVE links Paul Eggleton
2023-04-22  3:19 ` [PATCH 17/17] release-notes-4.2: add release notes Paul Eggleton
2023-04-22 10:01 ` Richard Purdie [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=f427391295df1ee31f77de7ffaa7cac103e66e72.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bluelightning@bluelightning.org \
    --cc=docs@lists.yoctoproject.org \
    --cc=michael.opdenacker@bootlin.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