From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH master 1/2] Documentation: migration-guides: split off 2026.02.0 into own file
Date: Wed, 25 Feb 2026 16:10:04 +0100 [thread overview]
Message-ID: <20260225151007.412926-1-a.fatoum@pengutronix.de> (raw)
Having a single migration-master.rst turns out to be error prone, because
presumably git detects the rename of the last release and adds new
entries not to migration-master.rst after the rebase, but to the
migration guide for the former release.
This seems to have happend with commit 09663fb38ffd
("startup: attempt poweroff if no shell and nothing to do"),
so move it back into the correct file and while at it add a
migration-master.rst right away.
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
.../migration-guides/migration-2026.01.0.rst | 9 ---------
.../migration-guides/migration-2026.02.0.rst | 11 +++++++++++
Documentation/migration-guides/migration-master.rst | 1 +
3 files changed, 12 insertions(+), 9 deletions(-)
create mode 100644 Documentation/migration-guides/migration-2026.02.0.rst
create mode 100644 Documentation/migration-guides/migration-master.rst
diff --git a/Documentation/migration-guides/migration-2026.01.0.rst b/Documentation/migration-guides/migration-2026.01.0.rst
index df7b3d6f497a..931972901695 100644
--- a/Documentation/migration-guides/migration-2026.01.0.rst
+++ b/Documentation/migration-guides/migration-2026.01.0.rst
@@ -36,12 +36,3 @@ ARM i.MX6 RIoTboard
The barebox update handler has been changed to write barebox to the
eMMC boot partitions rather than the user data area.
-
-CONFIG_SHELL_NONE
------------------
-
-If there's nothing to do for a shell-less barebox, it will now attempt
-to poweroff the system instead of busy-looping indefinitely.
-This changes behavior for systems that rely on a watchdog to reset
-a hanging barebox in this situation. If this breaks anything for you,
-please reach out.
diff --git a/Documentation/migration-guides/migration-2026.02.0.rst b/Documentation/migration-guides/migration-2026.02.0.rst
new file mode 100644
index 000000000000..80da34d32f5e
--- /dev/null
+++ b/Documentation/migration-guides/migration-2026.02.0.rst
@@ -0,0 +1,11 @@
+Release v2026.02.0
+==================
+
+CONFIG_SHELL_NONE
+-----------------
+
+If there's nothing to do for a shell-less barebox, it will now attempt
+to poweroff the system instead of busy-looping indefinitely.
+This changes behavior for systems that rely on a watchdog to reset
+a hanging barebox in this situation. If this breaks anything for you,
+please reach out.
diff --git a/Documentation/migration-guides/migration-master.rst b/Documentation/migration-guides/migration-master.rst
new file mode 100644
index 000000000000..8feca331c5d7
--- /dev/null
+++ b/Documentation/migration-guides/migration-master.rst
@@ -0,0 +1 @@
+:orphan:
--
2.47.3
next reply other threads:[~2026-02-25 15:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-25 15:10 Ahmad Fatoum [this message]
2026-02-25 15:10 ` [PATCH master 2/2] Documentation: migration-guides: 2026.01.0: clarify fsdev linux.bootargs change Ahmad Fatoum
2026-02-26 12:01 ` [PATCH master 1/2] Documentation: migration-guides: split off 2026.02.0 into own file Sascha Hauer
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=20260225151007.412926-1-a.fatoum@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.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