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, 29 Oct 2025 09:36:09 +0100 [thread overview]
Message-ID: <DDUO38T27G3T.1P7LBZ0Z45YIH@bootlin.com> (raw)
The following changes since commit fca48e1239950ccf10f6b1b805c5734104144ded:
vulnerabilities: update nvdcve file name (2025-10-13 09:13:46 +0200)
are available in the Git repository at:
git@push.yoctoproject.org:yocto-docs kirkstone-next
for you to fetch changes up to 073f3bca4c374b03398317e7f445d2440a287741:
ref-manual/classes.rst: document the relative_symlinks class (2025-10-27 17:09:19 +0100)
----------------------------------------------------------------
Antonin Godard (9):
ref-manual/variables.rst: document UNINATIVE_URL/CHECKSUM
ref-manual/classes.rst: extend the uninative class documentation
ref-manual/classes,variables: document the CCACHE_DISABLE variable
ref-manual/variables.rst: document the REQUIRED_MACHINE_FEATURES variable
ref-manual/variables.rst: document the REQUIRED_COMBINED_FEATURES variable
ref-manual/variables.rst: document the REQUIRED_IMAGE_FEATURES variable
ref-manual/variables.rst: document the USE_NLS variable
ref-manual/classes.rst: gettext: extend the documentation of the class
ref-manual/classes.rst: document the relative_symlinks class
João Marcos Costa (1):
variables.rst: fix LAYERDEPENDS description
Paul Barker (1):
dev-manual, test-manual: Update autobuilder output links
documentation/dev-manual/vulnerabilities.rst | 2 +-
documentation/ref-manual/classes.rst | 96 ++++++++++++++++++-----
documentation/ref-manual/variables.rst | 71 ++++++++++++++++-
documentation/test-manual/reproducible-builds.rst | 2 +-
documentation/test-manual/test-process.rst | 2 +-
5 files changed, 151 insertions(+), 22 deletions(-)
next reply other threads:[~2025-10-29 8:36 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-29 8:36 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-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-11-06 15:48 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=DDUO38T27G3T.1P7LBZ0Z45YIH@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