All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 6/6] toolchain-external: add Linaro ARM big endian toolchain
Date: Thu, 6 Mar 2014 23:41:57 +0100	[thread overview]
Message-ID: <20140306224157.GI3625@free.fr> (raw)
In-Reply-To: <20140306233051.7f4add0c@skate>

Thomas, All,

On 2014-03-06 23:30 +0100, Thomas Petazzoni spake thusly:
> On Thu, 06 Mar 2014 23:23:47 +0100, Peter Korsgaard wrote:
> >  > Linaro has started to release ARM big endian toolchains, so we
> >  > integrate this toolchain in the external toolchain logic of
> >  > Buildroot. Since ARM big endian is probably going to be a lot more
> >  > confidential than ARM little endian, we will only support one version
> > 
> > confidential? Do you mean 'specialized' or 'uncommon'?
> 
> Yes. In French "confidentiel" has two different meanings: it might mean
> "secret", or when talking about the usage, it can mean "rarely". I'll
> change to "uncommon", which is certainly better.

In english, "confidential" has the same meaning. It's even the first
listed in the Merriam Webster:

    http://www.merriam-webster.com/dictionary/confidential

    1. marked by intimacy or willingness to confide

But agreed, "uncommon" is easier to grok.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

      reply	other threads:[~2014-03-06 22:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-05 22:23 [Buildroot] [PATCH 0/6] External toolchain updates Thomas Petazzoni
2014-03-05 22:23 ` [Buildroot] [PATCH 1/6] toolchain-external: fix musl external support on x86 Thomas Petazzoni
2014-03-06  7:09   ` Arnout Vandecappelle
2014-03-05 22:23 ` [Buildroot] [PATCH 2/6] toolchain-external: add publicly available musl toolchains Thomas Petazzoni
2014-03-06  7:17   ` Arnout Vandecappelle
2014-03-05 22:23 ` [Buildroot] [PATCH 3/6] toolchain-external: bump Linaro ARM toolchains Thomas Petazzoni
2014-03-05 22:23 ` [Buildroot] [PATCH 4/6] toolchain-external: remove useless info in help text of " Thomas Petazzoni
2014-03-05 22:39   ` Yann E. MORIN
2014-03-05 22:23 ` [Buildroot] [PATCH 5/6] toolchain-external: bump Linaro AArch64 toolchains Thomas Petazzoni
2014-03-05 22:23 ` [Buildroot] [PATCH 6/6] toolchain-external: add Linaro ARM big endian toolchain Thomas Petazzoni
2014-03-06 22:23   ` Peter Korsgaard
2014-03-06 22:30     ` Thomas Petazzoni
2014-03-06 22:41       ` Yann E. MORIN [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=20140306224157.GI3625@free.fr \
    --to=yann.morin.1998@free.fr \
    --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 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.