From: Paul Eggleton <bluelightning@bluelightning.org>
To: docs@lists.yoctoproject.org
Cc: michael.opdenacker@bootlin.com
Subject: [PATCH 00/12] 4.3 release documentation
Date: Mon, 6 Nov 2023 23:29:30 +1300 [thread overview]
Message-ID: <cover.1699266393.git.bluelightning@bluelightning.org> (raw)
This is not 100% complete, but I wanted to send what I have now so that
we make progress and folks can review the changes so far.
Cheers
Paul
The following changes since commit 8fb31b507c37d2c11e9dc98559bd7d145e1dce04:
bsp-guide: bsp.rst: update beaglebone example (2023-11-03 15:35:05 +0100)
are available in the Git repository at:
https://git.yoctoproject.org/poky-contrib paule/4.3-release
https://git.yoctoproject.org/poky-contrib/log/?h=paule/4.3-release
Paul Eggleton (12):
Remove references to apm in MACHINE_FEATURES
ref-manual: update SDK_NAME variable documentation
ref-manual: remove semicolons from *PROCESS_COMMAND variables
release-notes-4.3: fix some typos
release-notes-4.3: tweaks to existing text
release-notes-4.3: add CVEs, recipe upgrades, license changes,
contributors
release-notes-4.3: remove the Distribution section
release-notes-4.3: move new classes to Rust section
release-notes-4.3: feature additions
migration-4.3: remove some unnecessary items
migration-4.3: adjustments to existing text
migration-4.3: additional migration items
documentation/dev-manual/new-machine.rst | 2 +-
.../migration-guides/migration-4.3.rst | 118 ++-
.../migration-guides/release-notes-4.3.rst | 704 +++++++++++++++++-
documentation/ref-manual/features.rst | 2 -
documentation/ref-manual/variables.rst | 51 +-
5 files changed, 801 insertions(+), 76 deletions(-)
--
2.34.1
next reply other threads:[~2023-11-06 10:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 10:29 Paul Eggleton [this message]
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 ` [docs] " Ulrich Ölmann
2023-11-06 16:14 ` 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=cover.1699266393.git.bluelightning@bluelightning.org \
--to=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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).