From: "Ulrich Ölmann" <u.oelmann@pengutronix.de>
To: Paul Eggleton <bluelightning@bluelightning.org>
Cc: michael.opdenacker@bootlin.com, docs@lists.yoctoproject.org
Subject: Re: [docs] [PATCH 09/12] release-notes-4.3: feature additions
Date: Mon, 06 Nov 2023 11:45:17 +0100 [thread overview]
Message-ID: <6rfs1ji2cj.fsf@pengutronix.de> (raw)
In-Reply-To: <dab7f691e3716938a7f05d62f0ff1a6026bc5ac8.1699266393.git.bluelightning@bluelightning.org>
Hi Paul,
thanks for sharing your work early!
On Mon, Nov 06 2023 at 23:29 +1300, "Paul Eggleton" <bluelightning@bluelightning.org> wrote:
> Some additional feature items from combing through commits (not 100%
> complete yet.)
>
> Signed-off-by: Paul Eggleton <bluelightning@bluelightning.org>
> ---
> .../migration-guides/release-notes-4.3.rst | 98 ++++++++++++++++++-
> 1 file changed, 96 insertions(+), 2 deletions(-)
>
> diff --git a/documentation/migration-guides/release-notes-4.3.rst b/documentation/migration-guides/release-notes-4.3.rst
> index dc689c30ada..07317888a7e 100644
> --- a/documentation/migration-guides/release-notes-4.3.rst
> +++ b/documentation/migration-guides/release-notes-4.3.rst
[...]
> @@ -225,6 +307,18 @@ New Features / Enhancements in 4.3
> :term:`SPLASH_IMAGES`, instead of a harder to generate and modify
> ``.h`` file.
>
> + - The ; character is no longer needed to separate functions specified in
> + :term:`IMAGE_POSTPROCESS_COMMAND`, :term:`IMAGE_POSTPROCESS_COMMAND`,
The term IMAGE_POSTPROCESS_COMMAND is enumerated twice here.
Best regards
Ulrich
> + :term:`POPULATE_SDK_POST_HOST_COMMAND`, :term:`ROOTFS_POSTINSTALL_COMMAND`
> + etc. (If any are present they will be replaced with spaces, so existing
> + metadata does not yet need to be changed.)
> +
> + - In the ``Upstream-Status`` field in a patch header, "Accepted" is no longer
> + a valid value since it is logically the same as "Backport". Change any
> + values you have (particularly in patches applied through bbappends for core
> + recipes, since they will be validated as indicated above).
> +
> +
> Known Issues in 4.3
> ~~~~~~~~~~~~~~~~~~~
--
Pengutronix e.K. | Ulrich Ölmann |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2023-11-06 10:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 10:29 [PATCH 00/12] 4.3 release documentation Paul Eggleton
2023-11-06 10:29 ` [PATCH 01/12] Remove references to apm in MACHINE_FEATURES Paul Eggleton
2023-11-06 10:29 ` [PATCH 02/12] ref-manual: update SDK_NAME variable documentation Paul Eggleton
2023-11-06 10:29 ` [PATCH 03/12] ref-manual: remove semicolons from *PROCESS_COMMAND variables Paul Eggleton
2023-11-06 10:29 ` [PATCH 04/12] release-notes-4.3: fix some typos Paul Eggleton
2023-11-06 10:29 ` [PATCH 05/12] release-notes-4.3: tweaks to existing text Paul Eggleton
2023-11-06 16:55 ` [docs] " Michael Opdenacker
2023-11-06 10:29 ` [PATCH 06/12] release-notes-4.3: add CVEs, recipe upgrades, license changes, contributors Paul Eggleton
2023-11-06 17:07 ` [docs] " Michael Opdenacker
2023-11-06 10:29 ` [PATCH 07/12] release-notes-4.3: remove the Distribution section Paul Eggleton
2023-11-06 10:29 ` [PATCH 08/12] release-notes-4.3: move new classes to Rust section Paul Eggleton
2023-11-06 10:29 ` [PATCH 09/12] release-notes-4.3: feature additions Paul Eggleton
2023-11-06 10:45 ` Ulrich Ölmann [this message]
2023-11-06 16:14 ` [docs] " Paul Eggleton
2023-11-06 10:29 ` [PATCH 10/12] migration-4.3: remove some unnecessary items Paul Eggleton
2023-11-06 10:29 ` [PATCH 11/12] migration-4.3: adjustments to existing text Paul Eggleton
2023-11-06 10:29 ` [PATCH 12/12] migration-4.3: additional migration items Paul Eggleton
2023-11-06 10:58 ` [docs] " Ulrich Ölmann
2023-11-06 16:16 ` Paul Eggleton
2023-11-06 20:45 ` Michael Opdenacker
2023-11-06 10:45 ` [PATCH 00/12] 4.3 release documentation Michael Opdenacker
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=6rfs1ji2cj.fsf@pengutronix.de \
--to=u.oelmann@pengutronix.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.