From: forsyth@caldo.demon.co.uk
To: 9fans@cse.psu.edu
Subject: Re: [9fans] File/cpu service provider
Date: Sat, 17 Jun 2000 09:10:24 +0100 [thread overview]
Message-ID: <200006170812.EAA17013@cse.psu.edu> (raw)
>> ... config managers like GNU Autoconf.
it's partly because Plan 9 does not need and never ought to need `Autoconf'
that it is so much easier to program, let alone `admin' than current UNIX derivatives/variants/clones.
<diatribe about autoconf, configure, and #ifdef removed>
next reply other threads:[~2000-06-17 8:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-17 8:10 forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-06-16 1:51 Russ Cox
2000-06-16 22:55 ` Richard Uhtenwoldt
2000-06-17 0:22 ` James G. Stallings II
2000-06-15 16:18 [9fans] File/cpu servers..? Russ Cox
2000-06-16 0:20 ` [9fans] File/cpu service provider Richard Uhtenwoldt
2000-06-16 9:15 ` Wesley Felter
2000-06-26 3:19 ` rob pike
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=200006170812.EAA17013@cse.psu.edu \
--to=forsyth@caldo.demon.co.uk \
--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).