From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] toolchain: Bump ARC tools to arc-2017.03-rc2
Date: Fri, 12 May 2017 21:15:35 +0200 [thread overview]
Message-ID: <20170512211535.555af2a5@free-electrons.com> (raw)
In-Reply-To: <20170512183104.37886-1-abrodkin@synopsys.com>
Hello,
On Fri, 12 May 2017 21:31:04 +0300, Alexey Brodkin wrote:
> This commit bumps ARC toolchain to arc-2017.03-rc2
>
> Please note that it is a release candidate and it might contain some
> breakages, please don't use it for production builds.
>
> Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com>
> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
What should we do in Buildroot master branch? We're currently using
arc-2017.03-rc1, which is also a release candidate. We are planning on
releasing Buildroot at the end of the month.
Should we pick -rc2 instead of -rc1 for this release ? We normally
don't upgrade components after Buildroot has released its -rc1, but I
guess we could make an exception since a release candidate is used for
ARC toolchain components.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-05-12 19:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-12 18:31 [Buildroot] [PATCH] toolchain: Bump ARC tools to arc-2017.03-rc2 Alexey Brodkin
2017-05-12 19:15 ` Thomas Petazzoni [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-05-12 19:47 Alexey Brodkin
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=20170512211535.555af2a5@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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