From: Abhey Shah <as234@york.ac.uk>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] the futility of #plan9 on irc
Date: Thu, 26 May 2005 10:17:15 +0100 [thread overview]
Message-ID: <dd7c80683b09a1aeea5af7f67d089c9c@york.ac.uk> (raw)
In-Reply-To: <3e1162e6050525094267cef8f9@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 774 bytes --]
Apologies for larding up the list with flippant Simpsons' quotes but
this one is appropriate for many situations.
Homer: There are three ways to do things: the right way, the wrong
way, and the Max Power way!
Bart: Isn't that just the wrong way?
Homer: Yeah, but faster!
On 25 May 2005, at 17:42, David Leimbach wrote:
>> The SCSI comment did get corrected, eventually, though
>> the comment about acme not being able to pipe a buffer
>> through an external program did not.
>>
>> Russ
>>
>
> Misinformation will continue to exist no matter what. People just get
> stuff wrong. They can even get it wrong here. I don't think removing
> IRC is going to solve that problem.
>
> IRC just allows you to be wrong faster :)
>
> Dave
>
>
[-- Attachment #2.1: Type: text/plain, Size: 282 bytes --]
from postmaster@ethel:
The following attachment had content that we can't
prove to be harmless. To avoid possible automatic
execution, we changed the content headers.
The original header was:
Content-Transfer-Encoding: 7bit
Content-Type: text/enriched;
charset=US-ASCII
[-- Attachment #2.2: file.suspect --]
[-- Type: application/octet-stream, Size: 862 bytes --]
Apologies for larding up the list with flippant Simpsons' quotes but
this one is appropriate for many situations.
<fontfamily><param>Verdana</param> Homer: There are three ways to do
things: the right way, the wrong way, and the Max Power way!
Bart: Isn't that just the wrong way?
Homer: Yeah, but faster!
</fontfamily>
On 25 May 2005, at 17:42, David Leimbach wrote:
<excerpt><excerpt>The SCSI comment did get corrected, eventually,
though
the comment about acme not being able to pipe a buffer
through an external program did not.
Russ
</excerpt>
Misinformation will continue to exist no matter what. People just get
stuff wrong. They can even get it wrong here. I don't think removing
IRC is going to solve that problem.
IRC just allows you to be wrong faster :)
Dave
</excerpt>
next prev parent reply other threads:[~2005-05-26 9:17 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-23 11:27 Russ Cox
2005-05-23 12:18 ` Vester Thacker
2005-05-23 17:44 ` Bruce Ellis
2005-05-23 17:46 ` Rob Pike
2005-05-23 18:43 ` Tim Newsham
2005-05-24 4:41 ` Dan Cross
2005-05-23 12:22 ` Uriel
2005-05-23 15:55 ` jmk
2005-05-24 0:54 ` Country Joe
2005-05-23 23:33 ` Chris Collins
2005-05-23 23:57 ` andrey mirtchovski
2005-05-24 0:03 ` Eric Van Hensbergen
2005-05-24 0:12 ` andrey mirtchovski
2005-05-24 4:29 ` Tim Newsham
2005-05-24 15:19 ` Russ Cox
2005-05-24 16:39 ` Vester Thacker
2005-05-24 16:43 ` William Josephson
2005-05-24 17:08 ` Vester Thacker
2005-05-26 4:02 ` McLone
2005-06-19 11:41 ` Vester Thacker
2005-06-19 11:43 ` Vester Thacker
2005-05-24 21:07 ` Chris Collins
2005-05-24 21:18 ` Russ Cox
2005-05-25 16:42 ` David Leimbach
2005-05-25 16:58 ` Bruce Ellis
2005-05-26 9:17 ` Abhey Shah [this message]
2005-05-24 21:20 ` Dan Cross
2005-05-24 21:31 ` Jack Johnson
2005-05-24 21:54 ` Devon H. O'Dell
2005-05-26 4:04 ` McLone
2005-05-26 4:19 ` Devon H. O'Dell
2005-05-26 4:29 ` Dan Cross
2005-05-24 4:46 ` Dan Cross
2005-05-24 5:29 ` Lucio De Re
2005-05-24 0:14 ` Skip Tavakkolian
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=dd7c80683b09a1aeea5af7f67d089c9c@york.ac.uk \
--to=as234@york.ac.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).