From: "Nigel Roles" <nigel@cotswold.demon.co.uk>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Remote access
Date: Wed, 23 Aug 2000 16:01:46 +0100 [thread overview]
Message-ID: <39A3F56A.26993.1C46D8A@localhost> (raw)
In-Reply-To: <002101c00d11$005bdf80$03c684c3@psychobasketcase.org>
Absolutely.
I particularly hate that gungy stuff which accumulates
in the plug hole.
>
> excellent analysis. i'm not opposed to adding in 3rd
> party stuff, but look what happened to linux; kitchen
> sink syndrome.
>
>
>
next prev parent reply other threads:[~2000-08-23 15:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-21 18:16 Russ Cox
2000-08-22 8:40 ` Douglas A. Gwyn
2000-08-22 12:45 ` Boyd Roberts
2000-08-22 17:49 ` Boyd Roberts
2000-08-23 14:47 ` Boyd Roberts
2000-08-23 15:01 ` Nigel Roles [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-08-21 16:30 Anthony Sorace
2000-08-21 13:21 rob pike
2000-08-21 9:52 forsyth
2000-08-21 11:25 ` Lucio De Re
2000-08-21 11:41 ` Lucio De Re
2000-08-21 14:29 ` Douglas A. Gwyn
2000-08-21 17:04 ` Boyd Roberts
2000-08-21 12:54 ` Wladimir Mutel
2000-08-21 14:28 ` Doug Henderson
2000-08-21 9:00 Chris Drelich
2000-08-21 9:27 ` Lucio De Re
2000-08-21 14:18 ` Douglas A. Gwyn
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=39A3F56A.26993.1C46D8A@localhost \
--to=nigel@cotswold.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).