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: Fri, 03 Jul 2026 09:49:51 +0200 [thread overview]
Message-ID: <DJORSCRU5ISJ.HTESMK2BJH95@bootlin.com> (raw)
The following changes since commit 78bd02a51fcc740180df95028c33045d23e31500:
migration-guides/migration-6.0.rst: fix wks file move note (2026-06-26 10:20:38 +0200)
are available in the Git repository at:
git@push.yoctoproject.org:yocto-docs wrynose-next
for you to fetch changes up to f5979d175971b55c4653ffe5c059d4e42034b714:
ref-manual/variables.rst: document the IMAGE_*_DEBUGFS variables (2026-07-03 09:33:01 +0200)
----------------------------------------------------------------
Antonin Godard (18):
dev-manual/wic.rst: replace deprecated wks directories
ref-manual/classes.rst: replace deprecated wks directory
ref-manual/kickstart.rst: replace deprecated wks directory
bsp-guide/bsp.rst: fix raspberry layer content example
dev-manual/wic.rst: remove note on wic-tools
dev-manual/wic.rst: remove bullet point on host requirements
dev-manual/wic.rst: add where to set IMAGE_FSTYPES/WKS_FILE[S] from
dev-manual/wic.rst: add a requirement to use wic from the build system
dev-manual/wic.rst: convert code snippet to code-blocks
ref-manual/kickstart.rst: remove note on available commands
ref-manual/kickstart.rst: document the include directive
ref-manual/variables.rst: document the CCACHE_NATIVE_RECIPES_ALLOWED variable
ref-manual/variables.rst: document missing CONFLICT_*_FEATURES variables
ref-manual/variables.rst: document the LOCALE_PATHS variable
ref-manual/variables.rst: document the TEST_SERIALCONTROL_CONNECT_TIMEOUT variable
ref-manual/variables.rst: document the LOCALE_UTF8_IS_DEFAULT variable
ref-manual/variables.rst: document the TEST_SERIALCONTROL_PS1 variable
ref-manual/variables.rst: document the IMAGE_*_DEBUGFS variables
Lee Chee Yang (1):
migration-guides: add add release notes for 6.0.1
Paul Barker (1):
recipe-style-guide: Clarify when License-Update tag is needed
Robert P. J. Day (2):
ref-manual: remove all traces of "kernel_menuconfig" task
dev-manual: update bmaptool section, refer to "bmaptool" package
documentation/bsp-guide/bsp.rst | 3 +-
.../contributor-guide/recipe-style-guide.rst | 9 +-
documentation/dev-manual/bmaptool.rst | 13 +-
documentation/dev-manual/wic.rst | 213 ++++++++++++------
documentation/migration-guides/release-6.0.rst | 1 +
.../migration-guides/release-notes-6.0.1.rst | 249 +++++++++++++++++++++
documentation/ref-manual/classes.rst | 3 +-
documentation/ref-manual/kickstart.rst | 24 +-
documentation/ref-manual/tasks.rst | 43 ++--
documentation/ref-manual/variables.rst | 83 ++++++-
10 files changed, 522 insertions(+), 119 deletions(-)
create mode 100644 documentation/migration-guides/release-notes-6.0.1.rst
next reply other threads:[~2026-07-03 7:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-03 7:49 Antonin Godard [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-07-15 13:19 [wrynose] Pull request Antonin Godard
2026-06-26 8:24 Antonin Godard
2026-06-22 8:45 Antonin Godard
2026-06-08 15:48 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=DJORSCRU5ISJ.HTESMK2BJH95@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