From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Thomas Perale <thomas.perale@mind.be>
Cc: buildroot@buildroot.org, Quentin Schulz <quentin.schulz@cherry.de>
Subject: Re: [Buildroot] [PATCH v3] docs/website: link LTS tooling documentation and staging branch
Date: Mon, 24 Aug 2026 21:18:52 +0200 [thread overview]
Message-ID: <aoyZCNzouS27J56C@windsurf> (raw)
In-Reply-To: <aoyY5FKwXCsNzMff@windsurf>
On Mon, Aug 24, 2026 at 09:18:18PM +0200, Thomas Petazzoni wrote:
> Hello,
>
> On Tue, Aug 11, 2026 at 03:43:12PM +0200, Thomas Perale via buildroot wrote:
> > 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>
>
> Thanks, applied to master!
Dammit no, scratch that. This is not the patch from you that I
applied, sorry about that.
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-08-24 19:19 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
2026-08-24 19:18 ` Thomas Petazzoni via buildroot
2026-08-24 19:18 ` Thomas Petazzoni via buildroot [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=aoyZCNzouS27J56C@windsurf \
--to=buildroot@buildroot.org \
--cc=quentin.schulz@cherry.de \
--cc=thomas.perale@mind.be \
--cc=thomas.petazzoni@bootlin.com \
/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