All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Joel Stanley <joel@jms.id.au>
Cc: Anisse Astier <anisse@astier.eu>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] package/go: Bump to v1.18.2
Date: Thu, 12 May 2022 10:47:57 +0200	[thread overview]
Message-ID: <87lev79lxe.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20220511114003.162006-1-joel@jms.id.au> (Joel Stanley's message of "Wed, 11 May 2022 21:10:02 +0930")

>>>>> "Joel" == Joel Stanley <joel@jms.id.au> writes:

 > Minor version bump to the latest release.
 > Signed-off-by: Joel Stanley <joel@jms.id.au>

According to to the upstream changelog this fixes security issues:

go1.18.2 (released 2022-05-10) includes security fixes to the syscall
package, as well as bug fixes to the compiler, runtime, the go command,
and the crypto/x509, go/types, net/http/httptest, reflect, and
sync/atomic packages

https://go.dev/doc/devel/release#go1.18

So I have reworded the commit message to make this clear and committed,
thanks.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2022-05-12  8:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-11 11:40 [Buildroot] [PATCH 1/2] package/go: Bump to v1.18.2 Joel Stanley
2022-05-11 11:40 ` [Buildroot] [PATCH 2/2] package/go: Fix link failure on ppc64 Joel Stanley
2022-09-18 16:20   ` Peter Korsgaard
2022-09-19  7:51     ` Joel Stanley
2022-05-12  8:47 ` Peter Korsgaard [this message]
2022-05-17  5:50   ` [Buildroot] [PATCH 1/2] package/go: Bump to v1.18.2 Joel Stanley
2022-05-17  6:26     ` Peter Korsgaard
2022-05-28  9:21 ` Peter Korsgaard

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=87lev79lxe.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=anisse@astier.eu \
    --cc=buildroot@buildroot.org \
    --cc=joel@jms.id.au \
    /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.