From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: docs@lists.yoctoproject.org
Subject: [scarthgap] Pull request
Date: Thu, 22 Aug 2024 11:36:18 +0200 [thread overview]
Message-ID: <2024082209361875d31de6@mail.local> (raw)
The following changes since commit 09e321d7cbd5bd7071a0c138e6d0c424fb086269:
migration-guides: add release notes for 5.0.2 (2024-06-27 18:22:27 +0200)
are available in the Git repository at:
git://git.yoctoproject.org/yocto-docs contrib/abelloni/scarthgap-next
for you to fetch changes up to fd4654df2d9eb36cae872dca4d23341ed5f9be91:
migration-guides: add release notes for 5.0.3 (2024-08-22 11:33:00 +0200)
----------------------------------------------------------------
Lee Chee Yang (2):
migration-guide: add release notes for 4.0.20
migration-guides: add release notes for 5.0.3
Matthias Pritschet (1):
ref-manual: fix typo and move SYSROOT_DIRS example
documentation/migration-guides/release-4.0.rst | 2 +
documentation/migration-guides/release-5.0.rst | 1 +
.../migration-guides/release-notes-4.0.20.rst | 130 +++++++++
.../migration-guides/release-notes-5.0.3.rst | 314 +++++++++++++++++++++
documentation/ref-manual/variables.rst | 48 ++--
5 files changed, 471 insertions(+), 24 deletions(-)
create mode 100644 documentation/migration-guides/release-notes-4.0.20.rst
create mode 100644 documentation/migration-guides/release-notes-5.0.3.rst
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next reply other threads:[~2024-08-22 9:36 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 9:36 Alexandre Belloni [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-04-02 14:38 [scarthgap] Pull request Antonin Godard
2026-03-30 8:42 Antonin Godard
2026-03-31 8:15 ` Paul Barker
2026-03-25 10:48 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-30 9:35 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-21 10:40 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-20 8:46 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:48 Alexandre Belloni
2024-09-09 7:17 Alexandre Belloni
2024-07-26 21:08 Alexandre Belloni
2024-06-27 16:29 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=2024082209361875d31de6@mail.local \
--to=alexandre.belloni@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