9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: David Yitzchak Cohen <dave@dave.tj>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] plan9 going to Hangar 18.
Date: Tue,  1 Apr 2003 18:40:27 -0500	[thread overview]
Message-ID: <20030401234027.GU23211@dave.tj> (raw)
In-Reply-To: <3E8A1A2F.7090604@linuxlink.com>

[-- Attachment #1: Type: text/plain, Size: 1951 bytes --]

/me loves reading mail on April 1st :-)

 - Dave


On Tue, Apr 01, 2003 at 05:01:03PM -0600, mike wrote:
> ROFLMAO
> 
> Russ Cox wrote:
> >Just a heads up.  After over 12 years of
> >leading the Plan 9 effort, we have finally
> >figured out that we just don't "get it."
> >About two months ago, after the last flame
> >war that finally showed us the error of our
> >ways, we started working with Hangar 18 to
> >transition all Plan 9 related development
> >activities to them.  The remaining lawyers
> >at Lucent have agreed to grant them a
> >non-transferable, non-exclusive license to
> >the Plan 9 technology, and hence-forth they
> >will be the main focal point around which
> >further Plan 9 related efforts will
> >revolve.  From now on, Jim Choate
> >(ravage@einstein.ssz.com) is the main
> >contact for all Plan 9 questions or issues.
> >Don't email 9trouble@plan9.bell-labs.com
> >anymore.  That just routes to /dev/null
> >until Jim can get igor finished.
> >
> >We made the decision to pass the reigns to
> >Hangar 18 because of their outstanding track
> >record of community contribution and their
> >clear, articulate vision of how Plan 9 can
> >help to mold the future of the world.  We
> >feel confident that they will provide an
> >excellent framework for others to build on.
> >We knew we were right when, after formally
> >closing the deal online, Hanger 18 sent each
> >of us a beautifully embroidered golf shirt
> >with the worlds, "tact sucks" emblazoned in
> >red across the front.
> >
> >As for us?  We'll go back to trying to port
> >Windows XP to ken's toaster.
> >
> >It's been a wild ride, and it was fun while
> >it lasted.
> >
> >Russ
> >
> >
> >
> 
> -- 
> Michael H. Collins	
> http://linuxlink.com
> 512-442-2009	512-656-9508

-- 
Uncle Cosmo, why do they call this a word processor?
It's simple, Skyler.  You've seen what food processors do to food, right?

[-- Attachment #2.1: Type: text/plain, Size: 246 bytes --]

The following attachment had content that we can't
prove to be harmless.  To avoid possible automatic
execution, we changed the content headers.
The original header was:

	Content-Type: application/pgp-signature
	Content-Disposition: inline

[-- Attachment #2.2: file.suspect --]
[-- Type: application/octet-stream, Size: 196 bytes --]

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+iiNrtSXacCAthpURAtBMAJ99pRHVKKlPWiPPGxm7kTDNtUrLtACfcPu/
B0I2GKPHtWXXRJKOkN0ai+4=
=qRPF
-----END PGP SIGNATURE-----

  reply	other threads:[~2003-04-01 23:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-01 21:28 Russ Cox
2003-04-01 21:40 ` [9fans] Competing April Fool's Jokes Joel Salomon
2003-04-01 21:47   ` Charles Forsyth
2003-04-01 23:01 ` [9fans] plan9 going to Hangar 18 mike
2003-04-01 23:40   ` David Yitzchak Cohen [this message]
2003-04-02  8:20 ` Anders Soendergaard
2003-04-03  1:06 okamoto

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=20030401234027.GU23211@dave.tj \
    --to=dave@dave.tj \
    --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).