From: Peter Korsgaard <peter@korsgaard.com>
To: Thomas Perale via buildroot <buildroot@buildroot.org>
Cc: Thomas Perale <thomas.perale@mind.be>,
Quentin Schulz <quentin.schulz@cherry.de>
Subject: Re: [Buildroot] [PATCH v3] docs/website: link LTS tooling documentation and staging branch
Date: Sun, 23 Aug 2026 21:46:37 +0200 [thread overview]
Message-ID: <871pbod3he.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20260811134312.170306-1-thomas.perale@mind.be> (Thomas Perale via buildroot's message of "Tue, 11 Aug 2026 15:43:12 +0200")
>>>>> "Thomas" == Thomas Perale via buildroot <buildroot@buildroot.org> writes:
> Users asked where the notes are available and if the information are
> publicly available.
> Those changes clearly explain the location and convention of the staging
> branches and also link to more documentation on how to read the
> annotations.
> Also update the timing of the different steps to be less specific.
> Signed-off-by: Thomas Perale <thomas.perale@mind.be>
> ---
> v1 -> v2: took into account review from https://lore.kernel.org/r/f6b4e9a2-8ee5-4799-960f-36dbf5710da6@cherry.de
> v2 -> v3: took into account review from https://lore.kernel.org/r/8d6fa46d-8200-454e-b5ac-aeccc4809647@cherry.de
Committed, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-08-23 19:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 13:43 [Buildroot] [PATCH v3] docs/website: link LTS tooling documentation and staging branch Thomas Perale via buildroot
2026-08-11 14:01 ` Quentin Schulz via buildroot
2026-08-11 14:07 ` Thomas Perale via buildroot
2026-08-23 19:46 ` Peter Korsgaard [this message]
2026-08-24 19:18 ` Thomas Petazzoni via buildroot
2026-08-24 19:18 ` Thomas Petazzoni via buildroot
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=871pbod3he.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=quentin.schulz@cherry.de \
--cc=thomas.perale@mind.be \
/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