From: Chris Faylor <cgf@cygnus.com>
To: Jason Molenda <jason-swarelist@molenda.com>
Cc: Jim Kingdon <kingdon@panix.com>, overseers@sourceware.cygnus.com
Subject: Re: sources.redhat.com is up
Date: Sat, 30 Dec 2000 06:08:00 -0000 [thread overview]
Message-ID: <20000702120828.D21037@cygnus.com> (raw)
In-Reply-To: <20000701231150.A27998@shell17.ba.best.com>
On Sat, Jul 01, 2000 at 11:11:50PM -0700, Jason Molenda wrote:
>On Sun, Jul 02, 2000 at 01:23:49AM -0400, Jim Kingdon wrote:
>
>> I've also updated
>> http://sources.redhat.com/sourceware/rename.html with the status as it
>> exists now.
>
>Hm. Just MHO, but I wouldn't expose the overseers list to the
>world and all its search engines like it is now. It's (obviously)
>an open list with no limited membership or mailing list archive
>visibility, but up to now it's been unlinked from the outside world.
>
>I guess I have visions of people sending bug reports ("Cygnus ls
>doesn't list my files on my DOS 3.2 partition!") and such to the
>list.
Hmm. I can't imagine *anyone* sending stuff like that. Why, that
would be completely clueless.
Oh. Wait. Now that you mention it, I guess I can imagine this.
cgf
WARNING: multiple messages have this Message-ID
From: Chris Faylor <cgf@cygnus.com>
To: Jason Molenda <jason-swarelist@molenda.com>
Cc: Jim Kingdon <kingdon@panix.com>, overseers@sourceware.cygnus.com
Subject: Re: sources.redhat.com is up
Date: Sun, 02 Jul 2000 09:08:00 -0000 [thread overview]
Message-ID: <20000702120828.D21037@cygnus.com> (raw)
Message-ID: <20000702090800.MGlwPvmU9cBMrHssFXF5PeGDk-18jtTxkAgWtLk9XuE@z> (raw)
In-Reply-To: <20000701231150.A27998@shell17.ba.best.com>
On Sat, Jul 01, 2000 at 11:11:50PM -0700, Jason Molenda wrote:
>On Sun, Jul 02, 2000 at 01:23:49AM -0400, Jim Kingdon wrote:
>
>> I've also updated
>> http://sources.redhat.com/sourceware/rename.html with the status as it
>> exists now.
>
>Hm. Just MHO, but I wouldn't expose the overseers list to the
>world and all its search engines like it is now. It's (obviously)
>an open list with no limited membership or mailing list archive
>visibility, but up to now it's been unlinked from the outside world.
>
>I guess I have visions of people sending bug reports ("Cygnus ls
>doesn't list my files on my DOS 3.2 partition!") and such to the
>list.
Hmm. I can't imagine *anyone* sending stuff like that. Why, that
would be completely clueless.
Oh. Wait. Now that you mention it, I guess I can imagine this.
cgf
next prev parent reply other threads:[~2000-12-30 6:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-30 6:08 Jim Kingdon
2000-06-29 7:27 ` Jim Kingdon
2000-12-30 6:08 ` Jeffrey A Law
2000-06-29 18:56 ` Jeffrey A Law
2000-12-30 6:08 ` Jim Kingdon
2000-07-01 22:23 ` Jim Kingdon
2000-12-30 6:08 ` Jason Molenda
2000-07-01 23:12 ` Jason Molenda
2000-12-30 6:08 ` Chris Faylor [this message]
2000-07-02 9:08 ` Chris Faylor
2000-12-30 6:08 ` Jim Kingdon
2000-07-02 7:19 ` Jim Kingdon
2000-12-30 6:08 ` Hans-Peter Nilsson
2000-06-30 3:26 ` Hans-Peter Nilsson
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=20000702120828.D21037@cygnus.com \
--to=cgf@cygnus.com \
--cc=jason-swarelist@molenda.com \
--cc=kingdon@panix.com \
--cc=overseers@sourceware.cygnus.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).