From: Peter Korsgaard <peter@korsgaard.com>
To: Christian Stewart <christian@aperture.us>
Cc: Julien Olivain <ju.o@free.fr>,
Julien Olivain via buildroot <buildroot@buildroot.org>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
James Hilliard <james.hilliard1@gmail.com>,
Thomas Perale <thomas.perale@mind.be>
Subject: Re: [Buildroot] [PATCH v2 1/1] package/go: security bump to version 1.26.1
Date: Sat, 14 Mar 2026 08:59:32 +0100 [thread overview]
Message-ID: <87wlzehme3.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CA+h8R2pDgzU6i3P1aLR_uPdd3baK0Kc=hV1oRbnbrHoBFbU7uA@mail.gmail.com> (Christian Stewart's message of "Fri, 13 Mar 2026 16:02:00 -0700")
>>>>> "Christian" == Christian Stewart <christian@aperture.us> writes:
Hi,
>> > NIT: It would have been better to first bump to 1.25.8 (which includes
>> > the same security fixes) and then afterwards add the feature bump from
>> > 1.25.x to 1.26.x so the security fix could be backported.
> I understand, will do in future.
Great!
> So, right now go1.26 is the latest, go1.25 is supported, and go1.24 is
> the oldest supported.
> Go1.23 isn't getting even security fixes anymore, so we should at
> least update the LTS branch to go1.24.
Yes, agreed.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-03-14 7:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 7:57 [Buildroot] [PATCH v2 1/1] package/go: security bump to version 1.26.1 Christian Stewart via buildroot
2026-03-12 19:44 ` Julien Olivain via buildroot
2026-03-13 17:14 ` Peter Korsgaard
2026-03-13 18:24 ` Julien Olivain via buildroot
2026-03-13 19:22 ` Peter Korsgaard
2026-03-13 23:02 ` Christian Stewart via buildroot
2026-03-14 7:59 ` Peter Korsgaard [this message]
2026-03-19 10:19 ` Thomas Perale via buildroot
2026-03-19 10:31 ` Peter Korsgaard
2026-03-19 11:19 ` Christian Stewart via buildroot
2026-03-20 15:54 ` Thomas Perale 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=87wlzehme3.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=christian@aperture.us \
--cc=james.hilliard1@gmail.com \
--cc=ju.o@free.fr \
--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