From: Jim Choate <ravage@einstein.ssz.com>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] Re: configure misery
Date: Wed, 4 Feb 2004 10:48:23 -0600 [thread overview]
Message-ID: <Pine.LNX.4.33.0402041045490.31157-100000@einstein.ssz.com> (raw)
In-Reply-To: <5865c95d8f1666473505421f775e92d7@vitanuova.com>
On Tue, 3 Feb 2004 rog@vitanuova.com wrote:
> [apologies to all for adding to this, but...]
>
> Jim: have you ever considered that the maxim "be strict in what
> you produce, but liberal in what you accept" can apply just as well
> to mailing list interactions as it does to computer protocols?
Absolutely, but one must draw a line somewhere. That somewhere in this
case is an 'institutionalized' bias in who can say what to whom.
May I ask, why you bothered to break your own suggestion?
I will close with a single addemdum, when people start thinking about what
they're saying -before- they post it I'll quit giving them crap for their
crap. I'm simply tired of seeing it.
-- --
Open Forge, LLC 24/365 Onsite Support for PCs, Networks, & Game Consoles
512-695-4126 (Austin, Tx.) help@open-forge.com irc.open-forge.com
Hangar 18 Open Source Distributed Computing Using Plan 9 & Linux
512-451-7087 http://open-forge.org/hangar18 irc.open-forge.org
James Choate 512-451-7087 ravage@ssz.com jchoate@open-forge.com
next prev parent reply other threads:[~2004-02-04 16:48 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200401300004.i0U04uD23642@peakunix.net>
2004-01-30 15:30 ` [9fans] Re: [hangar18-general] Frustration Jim Choate
2004-02-03 17:11 ` [9fans] Re: configure misery rog
2004-02-04 16:48 ` Jim Choate [this message]
2004-02-04 17:47 Spamm Trapp
-- strict thread matches above, loose matches on Subject: below --
2004-02-03 3:49 Li Yi
2004-02-03 11:30 ` Aharon Robbins
2004-02-03 13:32 ` a
2004-02-03 15:34 ` Jim Choate
2004-02-03 16:29 ` a
2004-02-03 14:18 ` andrey mirtchovski
2004-02-03 15:36 ` Jim Choate
2004-02-03 16:32 ` boyd, rounin
2004-02-03 16:42 ` Jim Choate
2004-02-03 23:53 ` David Presotto
2004-02-04 8:13 ` Aharon Robbins
2004-02-03 15:33 ` Jim Choate
2004-02-03 16:27 ` a
2004-02-03 16:44 ` Jim Choate
2004-02-03 16:53 ` andrey mirtchovski
2004-02-04 16:45 ` Jim Choate
2004-02-03 17:01 ` Wes Kussmaul
2003-11-16 8:04 Aharon Robbins
2003-11-16 8:37 ` Geoff Collyer
2003-11-16 14:46 ` Charles Forsyth
2003-11-16 9:53 ` Bruce Ellis
2003-11-16 19:11 ` Lyndon Nerenberg
2003-11-16 19:32 ` andrey mirtchovski
2003-11-16 21:43 ` Dan Cross
2003-11-16 23:37 ` Lyndon Nerenberg
2003-11-17 0:04 ` mirtchov
2003-11-17 0:04 ` boyd, rounin
2003-11-17 3:18 ` Dan Cross
2003-11-17 3:28 ` boyd, rounin
2003-11-16 21:46 ` Russ Cox
2003-11-16 22:24 ` mirtchov
2003-11-16 22:47 ` Russ Cox
2003-11-17 0:38 ` Mike Haertel
2003-11-16 22:38 ` Lyndon Nerenberg
2003-11-16 22:41 ` boyd, rounin
2003-11-18 12:54 ` Aharon Robbins
2003-11-18 14:11 ` Russ Cox
2003-11-18 14:55 ` Joel Salomon
2003-11-17 0:24 ` Enache Adrian
2003-11-17 12:16 ` Aharon Robbins
2003-11-17 23:16 ` Taj Khattra
2003-11-16 19:58 ` boyd, rounin
2003-11-17 12:25 ` Aharon Robbins
2003-11-17 0:42 ` John Stalker
2003-11-17 12:28 ` Aharon Robbins
2003-11-17 12:42 ` Lucio De Re
2003-11-17 12:53 ` Lucio De Re
2003-11-17 13:43 ` Aharon Robbins
2003-11-17 15:06 ` mirtchov
2003-11-17 15:35 ` David Presotto
2003-11-17 16:31 ` John Stalker
2003-11-17 17:19 ` Aharon Robbins
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=Pine.LNX.4.33.0402041045490.31157-100000@einstein.ssz.com \
--to=ravage@einstein.ssz.com \
--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).