9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Jeffrey Green <atallj@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] nice terminal...
Date: Mon, 23 Apr 2012 10:07:26 -0400	[thread overview]
Message-ID: <E60AB91A-2614-4561-96B4-B164FACE7FD5@gmail.com> (raw)
In-Reply-To: <CAJQxxwmwcLjoXzL1f97=rin5ayk-SvCOpcOqdSAvVdUAYTz4EA@mail.gmail.com>

On Apr 22, 2012, at 10:51 PM, Bruce Ellis wrote:

> "John Connor uses his 26th century technology to travel back in time,
> insisting that Sarah's destiny will be thwarted if she does not take
> the errata to the desert. They blow things up - not many dead. Sarah
> latches onto a Cyborg open wifi and summons - a sequel."

That may be a hard sell to Disney these days....

>
> On 23 April 2012 09:53, Joseph Stewart <joseph.stewart@gmail.com> wrote:
>> The whole Broadcom licensing thing is a major pain at my current job
>> (although my overlords probably have equally painful legal shackles).
>>
>> Not being able to see data sheets is pretty lame.
>>
>> -joe
>>
>>
>> On Mon, Apr 23, 2012 at 8:22 AM, Strake <strake888@gmail.com> wrote:
>>>
>>> On 22/04/2012, Jeff Sickel <jas@corpus-callosum.com> wrote:
>>>> Sign me up as a reviewer for your next theatrical production.  A little
>>>> radio, streaming audio, or even a youtube screening will suffice.
>>>>
>>>> On Apr 22, 2012, at 11:22 AM, Charles Forsyth wrote:
>>>>
>>>>> I always hope to see things like this appearing as the McGuffin in
>>>>> films:
>>>>> "The Broadcom Errata"
>>>>> (``Look! I've decoded the cryptogram in the K&R Code. It seems to give
>>>>> the
>>>>> location of a Broadcom data sheet.
>>>>> We thought they'd all been lost or destroyed!'' ``If it also has the
>>>>> errata, it would be priceless! That explains why they
>>>>> had to kill Fletcher to shut up his open source project.")
>>>
>>> I hope that 9fans will get the casting call.
>>>
>>
>
>
>
> --
> Don't meddle in the mouth -- MVS (0416935147, +1-513-3BRUCEE)
>




  reply	other threads:[~2012-04-23 14:07 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-20 12:33 Nicolas Bercher
2012-03-20 13:32 ` Calvin Morrison
2012-03-20 21:34   ` Stephen Wiley
2012-04-01 13:21   ` Paweł Lasek
2012-03-20 14:10 ` Charles Forsyth
2012-03-20 14:19   ` Richard Miller
2012-03-20 15:52     ` erik quanstrom
2012-03-20 16:03     ` David Leimbach
2012-03-20 14:59   ` Nicolas Bercher
2012-04-22 15:08   ` Jeffrey Green
2012-04-22 15:17     ` Tristan
2012-04-22 15:22       ` Devon H. O'Dell
2012-04-22 15:47         ` Jeffrey Green
2012-04-22 16:22           ` Charles Forsyth
2012-04-22 17:40             ` Jeff Sickel
2012-04-22 18:02               ` Devon H. O'Dell
2012-04-22 23:22               ` Strake
2012-04-22 23:53                 ` Joseph Stewart
2012-04-23  2:51                   ` Bruce Ellis
2012-04-23 14:07                     ` Jeffrey Green [this message]
2012-04-23 14:20                       ` Matthew Veety
2012-04-22 21:30           ` Bakul Shah
  -- strict thread matches above, loose matches on Subject: below --
2011-05-06 22:15 Gorka Guardiola
2011-05-06 22:35 ` Jason Dreisbach
2011-05-07  1:32 ` Skip Tavakkolian

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=E60AB91A-2614-4561-96B4-B164FACE7FD5@gmail.com \
    --to=atallj@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).