From: "Antonin Godard" <antonin.godard@bootlin.com>
To: "Richard Purdie" <richard.purdie@linuxfoundation.org>
Cc: <docs@lists.yoctoproject.org>
Subject: [kirkstone] Pull request
Date: Fri, 06 Jun 2025 19:15:23 +0200 [thread overview]
Message-ID: <DAFMBT128H1H.7552T07T40K4@bootlin.com> (raw)
The following changes since commit 76a4dd5ce041b38f4cab714017a38b035d9530a3:
ref-manual/variables.rst: document INHIBIT_UPDATERCD_BBCLASS (2025-05-26 09:48:14 +0200)
are available in the Git repository at:
git@push.yoctoproject.org:yocto-docs kirkstone-next
for you to fetch changes up to 92bc958301d0aeab0a19e75b8604f01770358195:
docs: conf.py: silence SyntaxWarning on js_splitter_code (2025-06-06 19:09:30 +0200)
----------------------------------------------------------------
Carlos Sánchez de La Lama (1):
ref-manual: clarify KCONFIG_MODE default behaviour
Lee Chee Yang (1):
migration-guides: add release notes for 4.0.27
Quentin Schulz (3):
docs: README: specify how to contribute instead of pointing at another file
deduplicate README
docs: conf.py: silence SyntaxWarning on js_splitter_code
Richard Purdie (1):
brief-yoctoprojectqs/ref-manual: Switch to new CDN
Robert P. J. Day (1):
Clean up explanation of minimum required version numbers
README | 32 +----
documentation/README | 21 ++-
documentation/brief-yoctoprojectqs/index.rst | 6 +-
documentation/conf.py | 2 +-
documentation/migration-guides/release-4.0.rst | 1 +
.../migration-guides/release-notes-4.0.27.rst | 153 +++++++++++++++++++++
documentation/ref-manual/variables.rst | 13 +-
7 files changed, 181 insertions(+), 47 deletions(-)
mode change 100644 => 120000 README
create mode 100644 documentation/migration-guides/release-notes-4.0.27.rst
next reply other threads:[~2025-06-06 17:15 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-06 17:15 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-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=DAFMBT128H1H.7552T07T40K4@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