From: Peter Korsgaard <peter@korsgaard.com>
To: Thomas Perale <thomas.perale@mind.be>
Cc: Christian Stewart <christian@aperture.us>,
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>
Subject: Re: [Buildroot] [PATCH v2 1/1] package/go: security bump to version 1.26.1
Date: Thu, 19 Mar 2026 11:31:22 +0100 [thread overview]
Message-ID: <87h5qcdsat.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20260319101938.68045-1-thomas.perale@mind.be> (Thomas Perale's message of "Thu, 19 Mar 2026 11:19:38 +0100")
>>>>> "Thomas" == Thomas Perale <thomas.perale@mind.be> writes:
Hi,
> I'm jumping into the discussion. As I'm not a Go user myself, how do you
> (Christian, Peter, anyone) see the update cycle for Go on the LTS branch.
> Should we update "late" to the last maintained subversion whenever LTS is based
> on a version no longer supported ?
> Is there any other source we can follow (Yocto, Debian ?).
> How much breaking changes are those subversion bump introducing ?
I am also not a go user, but what I have done in the past was to move to
the next release series when there was a new security vulnerability and
the series we were using in LTS was EOL.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-03-19 10:31 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
2026-03-19 10:19 ` Thomas Perale via buildroot
2026-03-19 10:31 ` Peter Korsgaard [this message]
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=87h5qcdsat.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