From: "Bruce Ellis" <bruce.ellis@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] gcc, kenc tidbits.
Date: Sun, 26 Mar 2006 23:36:16 +1000 [thread overview]
Message-ID: <775b8d190603260536j12b0df4co57a051c29f3fe64d@mail.gmail.com> (raw)
In-Reply-To: <6e35c0620603251717h4c28e7e4g640b17ec2164a11c@mail.gmail.com>
I think Boyd would say "f*ck them, c*cksuckers" and he'd have a
rational explanation of other's stupidity over a kier and and a steak.
that's only my 25 years of "hanging out, drinking and coding" with him.
brucee
On 3/26/06, Jack Johnson <knapjack@gmail.com> wrote:
> On 3/25/06, Brantley Coile <brantley@coraid.com> wrote:
> > Dang! I can't even get that right! How UN-Boyd like to present evidence.
>
> He might have appreciated that someone attempted to be Boyd-like and
> screwed it up.
>
> Hi Boyd.
next prev parent reply other threads:[~2006-03-26 13:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-25 21:44 Brantley Coile
2006-03-25 21:47 ` Brantley Coile
2006-03-26 1:17 ` Jack Johnson
2006-03-26 13:36 ` Bruce Ellis [this message]
2006-03-26 16:54 ` David Leimbach
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=775b8d190603260536j12b0df4co57a051c29f3fe64d@mail.gmail.com \
--to=bruce.ellis@gmail.com \
--cc=9fans@cse.psu.edu \
/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).