From: David Tolpin <dvd@davidashen.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] plan9 finished
Date: Sat, 28 Feb 2004 18:04:32 +0400 [thread overview]
Message-ID: <200402281404.i1SE4Wjj045826@adat.davidashen.net> (raw)
In-Reply-To: <5c7404f36d5425051f9af22b5031f210@borf.com>
> Plan 9 is finished because I can use it to do stuff other than develop Plan 9.
> Plan 9 isn't dead because it gets adapted to new hardare and user requirements.
> I written lots of code that is unfinished and dead.
The original poster used the word 'complete' as opposite to 'dead'.
What you name 'finished' is 'mature'.
David
next prev parent reply other threads:[~2004-02-28 14:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-28 11:30 matt
2004-02-28 11:37 ` David Tolpin
2004-02-28 12:45 ` matt
2004-02-28 13:00 ` David Tolpin
2004-02-28 13:22 ` David Presotto
2004-02-28 13:36 ` matt
2004-02-28 13:46 ` Brantley Coile
2004-02-28 14:04 ` David Tolpin [this message]
2004-02-28 15:11 ` andrey mirtchovski
2004-02-28 16:27 ` David Presotto
2004-02-28 13:27 ` matt
2004-02-28 13:29 ` David Tolpin
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=200402281404.i1SE4Wjj045826@adat.davidashen.net \
--to=dvd@davidashen.net \
--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).