From: Peter Korsgaard <peter@korsgaard.com>
To: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
Cc: "Yann E . MORIN" <yann.morin.1998@free.fr>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [PATCH 1/1] package/go: security bump to 1.19.2
Date: Sat, 05 Nov 2022 22:42:49 +0100 [thread overview]
Message-ID: <87iljtkrhi.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20221026215058.1e623bb4@windsurf> (Thomas Petazzoni via buildroot's message of "Wed, 26 Oct 2022 21:50:58 +0200")
>>>>> "Thomas" == Thomas Petazzoni via buildroot <buildroot@buildroot.org> writes:
> On Wed, 26 Oct 2022 12:35:08 -0700
> Christian Stewart via buildroot <buildroot@buildroot.org> wrote:
>> go1.19.2 includes security fixes to the archive/tar, net/http/httputil, and
>> regexp packages, as well as bug fixes to the compiler, the linker, the runtime,
>> and the go/types package.
>>
>> https://go.dev/doc/devel/release#go1.19
>> https://github.com/golang/go/issues?q=milestone%3AGo1.19.2+label%3ACherryPickApproved
>>
>> Signed-off-by: Christian Stewart <christian@paral.in>
>> ---
>> package/go/go.hash | 2 +-
>> package/go/go.mk | 2 +-
>> 2 files changed, 2 insertions(+), 2 deletions(-)
> Applied to master, thanks.
I have instead updated 2022.02.x and 2022.08.x to 1.18.8, which includes
the same security fixes.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-11-05 21:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-26 19:35 [Buildroot] [PATCH 1/1] package/go: security bump to 1.19.2 Christian Stewart via buildroot
2022-10-26 19:50 ` Thomas Petazzoni via buildroot
2022-11-05 21:42 ` Peter Korsgaard [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=87iljtkrhi.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.