From: <cej@gli.cas.cz>
To: <9fans@cse.psu.edu>
Subject: RE: [9fans] quantity vs. quality
Date: Thu, 8 Jun 2006 09:30:16 +0200 [thread overview]
Message-ID: <ACCF003CBA3D09458207DB0CB86AD17D2015AF@XMAIL.asuch.cas.cz> (raw)
> No, we need fresh ideas. An infinite number of monkeys turning Plan
> 9 into Linux is not progress.
I agree 100%. Although I would LOVE to have some loonix prgs w/o
rebooting to L. Or c++, java, perl, etc...
Attract more people to the clean design (and they will, hopefully,
rewrite everything that is(isn't;-) worth it...
IMHO.
++pac.
next reply other threads:[~2006-06-08 7:30 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-08 7:30 cej [this message]
2006-06-08 9:32 ` Lluís Batlle
2006-06-08 15:29 ` David Leimbach
2006-06-08 15:43 ` jmk
-- strict thread matches above, loose matches on Subject: below --
2006-06-09 6:01 cej
2006-06-08 0:53 [9fans] gcc on plan9 geoff
2006-06-08 1:07 ` Latchesar Ionkov
2006-06-08 1:39 ` [9fans] quantity vs. quality Lyndon Nerenberg
2006-06-08 3:05 ` Dan Cross
2006-06-08 3:44 ` Joel Salomon
2006-06-08 7:03 ` Roman Shaposhnik
2006-06-09 22:03 ` Roman Shaposhnick
2006-06-09 22:44 ` David Leimbach
2006-06-09 22:46 ` quanstro
2006-06-09 22:51 ` Latchesar Ionkov
2006-06-09 22:55 ` quanstro
2006-06-09 23:19 ` Latchesar Ionkov
2006-06-09 23:29 ` quanstro
2006-06-10 1:57 ` Latchesar Ionkov
2006-06-09 23:51 ` quanstro
2006-06-10 0:10 ` Roman Shaposhnick
2006-06-10 2:31 ` Latchesar Ionkov
2006-06-10 0:45 ` Roman Shaposhnick
2006-06-10 3:01 ` Latchesar Ionkov
2006-06-10 0:52 ` quanstro
2006-06-10 1:04 ` Roman Shaposhnick
2006-06-10 23:13 ` Ronald G Minnich
2006-06-11 0:44 ` quanstro
2006-06-11 5:08 ` lucio
2006-06-11 10:09 ` quanstro
2006-06-11 12:00 ` lucio
2006-06-11 22:59 ` quanstro
2006-06-11 23:26 ` geoff
2006-06-12 3:45 ` Paul Lalonde
2006-06-12 20:16 ` Ronald G Minnich
2006-06-12 20:23 ` Roman Shaposhnick
2006-06-12 20:56 ` Ronald G Minnich
2006-06-12 21:09 ` Victor Nazarov
2006-06-13 0:05 ` Roman Shaposhnik
2006-06-12 21:15 ` Francisco J Ballesteros
2006-06-13 12:08 ` rog
2006-06-13 16:34 ` Skip Tavakkolian
2006-06-13 21:35 ` "Nils O. Selåsdal"
2006-06-14 22:09 ` Roman Shaposhnick
2006-06-15 15:46 ` Victor Nazarov
2006-06-11 5:42 ` Russ Cox
2006-06-11 10:08 ` quanstro
2006-06-12 1:03 ` Roman Shaposhnik
2006-06-10 23:05 ` Ronald G Minnich
2006-06-11 0:00 ` quanstro
2006-06-10 0:24 ` andrey mirtchovski
2006-06-10 0:36 ` quanstro
2006-06-10 2:27 ` Latchesar Ionkov
2006-06-10 0:23 ` quanstro
2006-06-10 0:41 ` Paul Lalonde
2006-06-10 0:59 ` quanstro
2006-06-10 1:15 ` Paul Lalonde
2006-06-10 5:19 ` Bruce Ellis
2006-06-10 2:51 ` Latchesar Ionkov
2006-06-10 0:45 ` quanstro
2006-06-10 3:10 ` Latchesar Ionkov
2006-06-10 0:53 ` quanstro
2006-06-10 23:06 ` Ronald G Minnich
2006-06-10 23:15 ` geoff
2006-06-11 2:58 ` jmk
2006-06-10 23:04 ` Ronald G Minnich
2006-06-11 0:05 ` quanstro
2006-06-10 23:03 ` Ronald G Minnich
2006-06-09 23:25 ` Ronald G Minnich
2006-06-09 23:38 ` David Leimbach
2006-06-09 23:45 ` andrey mirtchovski
2006-06-09 23:46 ` Paul Lalonde
2006-06-10 23:03 ` Ronald G Minnich
2006-06-10 23:02 ` Ronald G Minnich
2006-06-11 0:12 ` quanstro
2006-06-11 2:20 ` Ronald G Minnich
2006-06-11 22:31 ` David Leimbach
2006-06-10 0:28 ` Roman Shaposhnick
2006-06-09 21:29 ` Roman Shaposhnick
2006-06-09 21:34 ` andrey mirtchovski
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=ACCF003CBA3D09458207DB0CB86AD17D2015AF@XMAIL.asuch.cas.cz \
--to=cej@gli.cas.cz \
--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).