From: Chris Faylor <cgf@cygnus.com>
To: Jason Molenda <jason@molenda.com>
Cc: overseers@sources.redhat.com, Hans-Peter Nilsson <hp@bitrange.com>
Subject: Re: Exposing hidden projects to ht://Dig indexing
Date: Tue, 25 Jul 2000 18:55:00 -0000 [thread overview]
Message-ID: <20000725215530.A26583@cygnus.com> (raw)
Message-ID: <20000725185500.6J0QhdWcKBKR9hIuv245gj7HQYf5GalJ7rWAqQT4-_Y@z> (raw)
In-Reply-To: <20000725184556.A23055@shell17.ba.best.com>
On Tue, Jul 25, 2000 at 06:45:56PM -0700, Jason Molenda wrote:
>On Tue, Jul 25, 2000 at 09:23:51PM -0400, Chris Faylor wrote:
>> I would like to vote that overseers should definitely not be archived in
>> a public place.
>
>Do you mean that it should not be archived, access to its archives
>should be restricted (e.g. requiring passwords to get at the
>archives), or that we should not advertise links to the archive
>publically?
>
>I personally prefer the latter. I don't really care about people
>on the net reading these notes--all content here is either technical
>(which I doubt anyone would argue should be hidden) or policy (which
>I guess some could argue should be hidden to avoid repeated debates)
>related.
The latter.
>I do want to keep this list free of random e-mails from folks on
>the net. If a user/developer on a sourceware project is having a
>problem, that problem should come to the overseers list via that
>project's maintainer. The maintainer will (with luck) be clueful
>enough to filter out the non-problems and FAQs, and only report
>new, novel problems.
Yup.
cgf
next prev parent reply other threads:[~2000-07-25 18:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-30 6:08 Hans-Peter Nilsson
2000-07-25 17:58 ` Hans-Peter Nilsson
2000-12-30 6:08 ` Chris Faylor
2000-07-25 18:24 ` Chris Faylor
2000-12-30 6:08 ` Hans-Peter Nilsson
2000-07-25 18:43 ` Hans-Peter Nilsson
2000-12-30 6:08 ` Jason Molenda
2000-07-25 18:46 ` Jason Molenda
2000-12-30 6:08 ` Chris Faylor [this message]
2000-07-25 18:55 ` Chris Faylor
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=20000725215530.A26583@cygnus.com \
--to=cgf@cygnus.com \
--cc=hp@bitrange.com \
--cc=jason@molenda.com \
--cc=overseers@sources.redhat.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).