From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org, Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: Re: [PATCH] Documentation: add migration guide for v2025.05.0
Date: Tue, 06 May 2025 09:18:15 +0200 [thread overview]
Message-ID: <174651589552.3187934.14888282624492920097.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20250505140746.2583140-1-a.fatoum@pengutronix.de>
On Mon, 05 May 2025 16:07:46 +0200, Ahmad Fatoum wrote:
> To simplify barebox updates, let's commit to the documentation a guide
> about potential breakage that users and integrators may run into after
> an update, e.g. renamed Kconfig symbols.
>
> This is inspired by the migration guides of the Yocto project[1].
>
> [1]: https://docs.yoctoproject.org/3.4/migration-guides/migration-3.4.html
>
> [...]
Applied, thanks!
[1/1] Documentation: add migration guide for v2025.05.0
https://git.pengutronix.de/cgit/barebox/commit/?id=88a2114596bd (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
prev parent reply other threads:[~2025-05-06 7:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-05 14:07 Ahmad Fatoum
2025-05-06 7:18 ` Sascha Hauer [this message]
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=174651589552.3187934.14888282624492920097.b4-ty@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=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