From: David Given <dg@cowlark.com>
To: MFLD <mfld.fr@gmail.com>, linux-8086@vger.kernel.org
Subject: Re: Right BCC version to use ?
Date: Fri, 27 Mar 2015 22:57:48 +0100 [thread overview]
Message-ID: <5515D25C.9010201@cowlark.com> (raw)
In-Reply-To: <55159B76.9000806@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 562 bytes --]
On 27/03/15 19:03, MFLD wrote:
[...]
> I am afraid moving the current build chain to another compiler is too
> ambitious... and selecting another "exotic" compiler would not bring us
> back into the mainstream...
Yeah, I know, alas... I mentioned it because it's ANSI, it's small, and
it exists (which many people don't know).
--
┌─── ｄｇ＠ｃｏｗｌａｒｋ．ｃｏｍ ───── http://www.cowlark.com ─────
│
│ "Sufficiently advanced incompetence is indistinguishable from
│ malice." -- Vernon Schryver
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2015-03-27 21:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 7:05 Right BCC version to use ? MFLD
2015-03-24 11:30 ` Jody Bruchon
2015-03-24 21:50 ` David Given
2015-03-27 18:03 ` MFLD
2015-03-27 21:57 ` David Given [this message]
2015-03-27 22:12 ` Jody Bruchon
2015-03-27 22:33 ` MFLD
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=5515D25C.9010201@cowlark.com \
--to=dg@cowlark.com \
--cc=linux-8086@vger.kernel.org \
--cc=mfld.fr@gmail.com \
/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