From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/go: bump to version 1.12.1
Date: Sun, 17 Mar 2019 11:09:38 +0100 [thread overview]
Message-ID: <20190317110938.2b5a9ce2@windsurf> (raw)
In-Reply-To: <20190317020142.743-1-christian@paral.in>
Hello,
On Sat, 16 Mar 2019 19:01:42 -0700
Christian Stewart <christian@paral.in> wrote:
> Go 1.12 was released on 2/25/2019: https://blog.golang.org/go1.12
>
> Go 1.12.1 was released on 3/14/2019:
> https://golang.org/doc/devel/release.html#go1.12.minor
>
> Additional notes on how Go modules will evolve in 2019 are here:
> https://blog.golang.org/modules2019
>
> In Go 1.12, module support remains the same as in Go 1.11. GOPATH is scheduled
> for deprecation in 1.13, however. The Buildroot Go package infrastructure should
> therefore aim to migrate to a new, currently undefined, Go module friendly
> compilation approach before Go 1.13 is released.
>
> Signed-off-by: Christian Stewart <christian@paral.in>
>
> package/go: bump to 1.12.1
>
> Signed-off-by: Christian Stewart <christian@paral.in>
There was a mistake here in the commit log, I fixed that up when applying.
> ---
> package/go/go.hash | 2 +-
> package/go/go.mk | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2019-03-17 10:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-17 2:01 [Buildroot] [PATCH 1/1] package/go: bump to version 1.12.1 Christian Stewart
2019-03-17 10:09 ` Thomas Petazzoni [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=20190317110938.2b5a9ce2@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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