From: "Antonin Godard" <antonin.godard@bootlin.com>
To: "Richard Purdie" <richard.purdie@linuxfoundation.org>
Cc: <docs@lists.yoctoproject.org>
Subject: [kirkstone] Pull request
Date: Wed, 06 Nov 2024 16:48:20 +0100 [thread overview]
Message-ID: <D5F7PNWXHQGQ.1LP3EUZW7EEP0@bootlin.com> (raw)
The following changes since commit fe98cb44fd52e2e455255be33aacf60f12dd5bad:
release-notes-4.0,brief-yoctoprojectqs: update BB_HASHSERVE_UPSTREAM for new infrastructure (2024-11-04 08:49:32 +0000)
are available in the Git repository at:
git@push.yoctoproject.org:yocto-docs kirkstone-next
for you to fetch changes up to 1f61cd4a3e9c5bf75910559ddf2372f921c2a4ef:
ref-manual: variables: add SIGGEN_LOCKEDSIGS* variables (2024-11-06 16:40:47 +0100)
----------------------------------------------------------------
Notes:
- Adapt "ref-manual: devtool-reference: document missing commands" to remove
the part on "ide-sdk".
- Do not pick the bblock commit from Julien, bblock is not backported on kirkstone.
- Pick a commit from Michael to provide description for Sysroot, I was getting
an error with newer versions of Sphinx.
----------------------------------------------------------------
Antonin Godard (2):
ref-manual: devtool-reference: document missing commands
conf.py: rename :cve: role to :cve_nist:
Julien Stephan (4):
README: add instruction to run Vale on a subset
documentation: Makefile: add SPHINXLINTDOCS to specify subset to sphinx-lint
styles: vocabularies: Yocto: add sstate
ref-manual: variables: add SIGGEN_LOCKEDSIGS* variables
Michael Opdenacker (1):
ref-manual: add description for the "sysroot" term
documentation/Makefile | 23 ++++----
documentation/README | 18 +++++-
documentation/conf.py | 2 +-
.../contributor-guide/recipe-style-guide.rst | 2 +-
.../migration-guides/release-notes-3.4.1.rst | 14 ++---
.../migration-guides/release-notes-3.4.2.rst | 42 ++++++-------
.../migration-guides/release-notes-3.4.3.rst | 10 ++--
.../migration-guides/release-notes-3.4.4.rst | 6 +-
.../migration-guides/release-notes-3.4.rst | 56 +++++++++---------
.../migration-guides/release-notes-4.0.1.rst | 10 ++--
.../migration-guides/release-notes-4.0.10.rst | 42 ++++++-------
.../migration-guides/release-notes-4.0.11.rst | 24 ++++----
.../migration-guides/release-notes-4.0.12.rst | 48 +++++++--------
.../migration-guides/release-notes-4.0.13.rst | 68 +++++++++++-----------
.../migration-guides/release-notes-4.0.14.rst | 56 +++++++++---------
.../migration-guides/release-notes-4.0.15.rst | 34 +++++------
.../migration-guides/release-notes-4.0.16.rst | 30 +++++-----
.../migration-guides/release-notes-4.0.17.rst | 42 ++++++-------
.../migration-guides/release-notes-4.0.18.rst | 32 +++++-----
.../migration-guides/release-notes-4.0.19.rst | 36 ++++++------
.../migration-guides/release-notes-4.0.2.rst | 14 ++---
.../migration-guides/release-notes-4.0.20.rst | 16 ++---
.../migration-guides/release-notes-4.0.21.rst | 48 +++++++--------
.../migration-guides/release-notes-4.0.22.rst | 30 +++++-----
.../migration-guides/release-notes-4.0.3.rst | 30 +++++-----
.../migration-guides/release-notes-4.0.4.rst | 22 +++----
.../migration-guides/release-notes-4.0.5.rst | 10 ++--
.../migration-guides/release-notes-4.0.6.rst | 44 +++++++-------
.../migration-guides/release-notes-4.0.7.rst | 40 ++++++-------
.../migration-guides/release-notes-4.0.8.rst | 20 +++----
.../migration-guides/release-notes-4.0.9.rst | 42 ++++++-------
.../migration-guides/release-notes-4.0.rst | 62 ++++++++++----------
documentation/ref-manual/devtool-reference.rst | 32 +++++++++-
documentation/ref-manual/terms.rst | 25 ++++++++
documentation/ref-manual/variables.rst | 44 ++++++++++++++
.../styles/config/vocabularies/Yocto/accept.txt | 1 +
36 files changed, 596 insertions(+), 479 deletions(-))
next reply other threads:[~2024-11-06 15:48 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-06 15:48 Antonin Godard [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-04-02 14:38 [kirkstone] Pull request Antonin Godard
2026-03-05 17:13 Antonin Godard
2026-02-27 10:00 Antonin Godard
2026-02-11 14:40 Antonin Godard
2026-01-13 9:54 Antonin Godard
2025-12-24 9:04 Antonin Godard
2025-12-11 10:23 Antonin Godard
2025-11-14 17:16 Antonin Godard
2025-10-29 8:36 Antonin Godard
2025-10-20 7:27 Antonin Godard
2025-10-13 16:36 Antonin Godard
2025-10-03 15:01 Antonin Godard
2025-09-26 8:52 Antonin Godard
2025-09-12 14:54 Antonin Godard
2025-08-08 16:43 Antonin Godard
2025-08-01 10:12 Antonin Godard
2025-07-11 8:34 Antonin Godard
2025-06-27 8:43 Antonin Godard
2025-06-20 7:43 Antonin Godard
2025-06-06 17:15 Antonin Godard
2025-05-26 7:55 Antonin Godard
2025-05-16 14:04 Antonin Godard
2025-04-11 7:10 Antonin Godard
2025-03-07 16:37 Antonin Godard
2025-02-25 16:56 Antonin Godard
2025-02-14 13:27 Antonin Godard
2025-02-07 9:03 Antonin Godard
2025-01-27 15:58 Antonin Godard
2025-01-20 8:39 Antonin Godard
2025-01-08 16:00 Antonin Godard
2024-12-27 14:02 Antonin Godard
2024-12-16 8:24 Antonin Godard
2024-11-29 8:07 Antonin Godard
2024-11-15 8:04 Antonin Godard
2024-10-31 12:47 Antonin Godard
2024-10-25 8:37 Antonin Godard
2024-10-18 7:33 Antonin Godard
2024-10-08 13:50 Alexandre Belloni
2024-09-09 7:18 Alexandre Belloni
2024-08-22 9:35 Alexandre Belloni
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=D5F7PNWXHQGQ.1LP3EUZW7EEP0@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=richard.purdie@linuxfoundation.org \
/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