From: Bruce Ellis <bruce.ellis@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] fortune nomination
Date: Fri, 1 Feb 2013 21:59:01 +1100 [thread overview]
Message-ID: <CAJQxxwmVPfBnrj=_T5fqxN-VzLX4XOUOkJGOAXV1n8YJLfB0yg@mail.gmail.com> (raw)
In-Reply-To: <CAGWMD9GETrsmW61UJxV24Mrf2QNU9cU8RYb=EhEo4JHOKZZB-w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 780 bytes --]
10 years ago the gcc manual was bigger than kenc source.
take your pick. learn about a neat compiler or read the gcc manual.
brucee
On 1 February 2013 06:19, Rox 64 <mrox128@gmail.com> wrote:
> On Thu, Jan 31, 2013 at 6:39 PM, <tlaronde@polynum.com> wrote:
>
>> Ah! I think I know why compile binaries with gcc are so slow. Because
>> they first found the answer: GNU Public Licence. Then they said: here is
>> the answer! Uh! THAT??? But answer to what? Hence now gcc embeds code to
>> find the question the GPL is the answer for.
>
>
> I'm not sure if I should take it as a joke. You can never know what's
> going to be the next move of our saviors the Fat Software Foundation.
>
--
Don't meddle in the mouth -- MVS (0416935147, +1-513-3BRUCEE)
[-- Attachment #2: Type: text/html, Size: 1467 bytes --]
next prev parent reply other threads:[~2013-02-01 10:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-31 4:51 erik quanstrom
2013-01-31 14:20 ` tlaronde
2013-01-31 17:44 ` Rox 64
2013-01-31 17:56 ` Charles Forsyth
2013-01-31 17:59 ` Kurt H Maier
2013-01-31 18:08 ` Rox 64
2013-01-31 18:12 ` Kurt H Maier
2013-01-31 17:39 ` tlaronde
2013-01-31 19:19 ` Rox 64
2013-02-01 10:59 ` Bruce Ellis [this message]
2013-01-31 18:16 ` andrey mirtchovski
2013-02-01 11:56 ` Nicolas Bercher
2013-02-01 16:34 ` phineas.pett
2013-01-31 17:42 ` Matthew Veety
2013-01-31 16:50 ` tlaronde
2013-02-21 13:56 dexen deVries
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='CAJQxxwmVPfBnrj=_T5fqxN-VzLX4XOUOkJGOAXV1n8YJLfB0yg@mail.gmail.com' \
--to=bruce.ellis@gmail.com \
--cc=9fans@9fans.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;
as well as URLs for NNTP newsgroup(s).