From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC PATCH v1 1/1] package/go: bump to go 1.15.1
Date: Sun, 6 Sep 2020 14:32:32 +0200 [thread overview]
Message-ID: <20200906143232.0a74af66@windsurf.home> (raw)
In-Reply-To: <CA+h8R2oMbeHLEQ09M-0SK34cvqHU9hA0tJc7MbX_vxAU6Tjnqw@mail.gmail.com>
On Sat, 5 Sep 2020 22:56:09 -0700
Christian Stewart <christian@paral.in> wrote:
> FYI, did not mean to flag this as [RFC], just for "next".
We don't have a "next" branch at the moment. It only exists between
-rc1 and the final release. So I've applied to master.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-09-06 12:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-06 5:51 [Buildroot] [RFC PATCH v1 1/1] package/go: bump to go 1.15.1 Christian Stewart
2020-09-06 5:56 ` Christian Stewart
2020-09-06 12:32 ` Thomas Petazzoni [this message]
2020-09-06 12:32 ` Thomas Petazzoni
-- strict thread matches above, loose matches on Subject: below --
2020-09-06 5:57 [Buildroot] [PATCH v1 1/1] package/go: bump to go 1.14.8 Christian Stewart
2020-09-06 5:57 ` [Buildroot] [RFC PATCH v1 1/1] package/go: bump to go 1.15.1 Christian Stewart
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=20200906143232.0a74af66@windsurf.home \
--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