From: "Antonin Godard" <antonin.godard@bootlin.com>
To: "Paul Barker" <paul@pbarker.dev>
Cc: <docs@lists.yoctoproject.org>, "Yoann Congal" <yoann.congal@smile.fr>
Subject: [wrynose] Pull request
Date: Mon, 22 Jun 2026 10:45:29 +0200 [thread overview]
Message-ID: <DJFG2YJFWT7W.2JF07UGMTTS18@bootlin.com> (raw)
The following changes since commit 768cbc95861c0da961c9f1ba77a9369caa3dce2d:
migration-guide: add release notes for 5.0.18 (2026-06-08 17:25:28 +0200)
are available in the Git repository at:
git@push.yoctoproject.org:yocto-docs wrynose-next
for you to fetch changes up to 2c59a23fc39d92831cb55a0e5f713d20f94730d4:
ref-manual: add more explanation to glossary variable LICENSE (2026-06-22 10:37:34 +0200)
----------------------------------------------------------------
Antonin Godard (1):
Document shared state signing
Peter Marko (1):
build-manual: update ROOTFS_POSTPROCESS_COMMAND example
Robert P. J. Day (14):
ref-manual: clarify that PACKAGE_EXCLUDE supports DEB packaging
dev-manual: drop "PREFERRED_VERSION" from x86-base.inc snippet
dev-manual: change "setup" to "set up" when used as an action
dev-manual: fix grammatical error, missing word "with"
dev-manual: fix broken grammar in "Libraries" section
dev-manual: fully define SOLIBS-related variables in bitbake.conf
security-manual: some grammar and wording fixes in intro
kernel-dev: remove references to defunct LTSI project
dev-manual: update AUTOREV explanation to match current file
dev-manual: SysVinit is the default init manager for Poky
ref-manual: clarify use of "PACKAGE_ARCH" in a packagegroup
ref-manual: document RM_WORK_EXCLUDE_ITEMS variable
ref-manual: update glossary entries for packaging backend variables
ref-manual: add more explanation to glossary variable LICENSE
Vyacheslav Yurkov (1):
migration-guide: Fix migration scripts
documentation/dev-manual/build-quality.rst | 2 +-
documentation/dev-manual/building.rst | 2 +-
documentation/dev-manual/external-scm.rst | 45 ++--
documentation/dev-manual/hashequivserver.rst | 4 +-
documentation/dev-manual/init-manager.rst | 2 +-
documentation/dev-manual/libraries.rst | 2 +-
documentation/dev-manual/new-recipe.rst | 5 +-
documentation/dev-manual/poky-manual-setup.rst | 10 +-
documentation/dev-manual/prebuilt-libraries.rst | 4 +-
documentation/dev-manual/start.rst | 8 +-
documentation/kernel-dev/concepts-appx.rst | 16 --
documentation/kernel-dev/intro.rst | 6 +-
documentation/migration-guides/migration-5.3.rst | 6 +-
documentation/overview-manual/concepts.rst | 6 +
documentation/ref-manual/classes.rst | 19 ++
documentation/ref-manual/variables.rst | 79 ++++++-
documentation/security-manual/index.rst | 1 +
documentation/security-manual/intro.rst | 14 +-
documentation/security-manual/sstate-signing.rst | 285 +++++++++++++++++++++++
19 files changed, 438 insertions(+), 78 deletions(-)
create mode 100644 documentation/security-manual/sstate-signing.rst
next reply other threads:[~2026-06-22 8:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-22 8:45 Antonin Godard [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-06-08 15:48 [wrynose] Pull request Antonin Godard
2026-05-19 13:51 Antonin Godard
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=DJFG2YJFWT7W.2JF07UGMTTS18@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=paul@pbarker.dev \
--cc=yoann.congal@smile.fr \
/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