Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/5] toolchain/external: rename Linaro arm and AArch64 options
Date: Mon, 21 Sep 2015 19:17:18 +0200	[thread overview]
Message-ID: <56003B9E.4050108@mind.be> (raw)
In-Reply-To: <86fd4e995ad6ec4737cdd0b0c3a5c4c0f9a0123a.1442785491.git.yann.morin.1998@free.fr>

On 20-09-15 23:45, Yann E. MORIN wrote:
> We're going to add a new Linaro version (2015.02) for those toolchains,
> so we want to differentiate them.
> 
> Even though we could simply keep the current options as-is and just
> introduce the new ones suffixed with the version, it is better to rename
> the existing options for consistency with the new ones and wiith other
> multi-versions toolchains (like the CS CodeBench).

 Sorry to revisit the discussion on IRC, but in be2abf23 Thomas Petazzoni wrote:

    Linaro toolchains are released so frequently (every month) that it
    doesn't make much sense to support 3 consecutive versions. So, like we
    do for ARM big-endian, let's support only one version at a time.

 Are we in agreement that this has changed because it seems they now have stable
releases? Or let me put this differently: are we sure now that the 2015.02
version is really considered more stable than 2015.08, or is it just that
they're too lazy to update their website?

 Regards,
 Arnout


[snip]

-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

  reply	other threads:[~2015-09-21 17:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-20 21:45 [Buildroot] [PATCH 0/5] toolchain/external: bump the Linaro toolchains (branch yem/toolchain-linaro-2015.02-2) Yann E. MORIN
2015-09-20 21:45 ` [Buildroot] [PATCH 1/5] toolchain/external: commonalise comments about Linaro toolchains Yann E. MORIN
2015-10-04 17:34   ` Thomas Petazzoni
2015-09-20 21:45 ` [Buildroot] [PATCH 2/5] toolchain/external: rename Linaro arm and AArch64 options Yann E. MORIN
2015-09-21 17:17   ` Arnout Vandecappelle [this message]
2015-09-21 20:45     ` Yann E. MORIN
2015-09-20 21:45 ` [Buildroot] [PATCH 3/5] toolchain/external: bump Linaro to 2015.12 for ARM (LE) Yann E. MORIN
2015-09-20 21:45 ` [Buildroot] [PATCH 4/5] toolchain/external: bump Linaro to 2015.12 for ARM (BE) Yann E. MORIN
2015-09-21 12:28   ` Romain Naour
2015-09-21 17:29     ` Yann E. MORIN
2015-09-20 21:45 ` [Buildroot] [PATCH 5/5] toolchain/external: bump Linaro to 2015.12 for AArch64 (LE) Yann E. MORIN

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=56003B9E.4050108@mind.be \
    --to=arnout@mind.be \
    --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