From: Jim Kingdon <kingdon@redhat.com>
To: cgf@cygnus.com
Cc: jlarmour@redhat.co.uk, overseers@sourceware.cygnus.com
Subject: Re: ORBS redux, round n
Date: Sat, 30 Dec 2000 06:08:00 -0000 [thread overview]
Message-ID: <200003241754.MAA23805@devserv.devel.redhat.com> (raw)
In-Reply-To: <20000324120154.A3986@cygnus.com>
1. I have added Chris Faylor and Jonathan Larmour to the sourceware
group. Don't upload trojan horses. Be careful. Buy low, sell high.
2. I don't plan to _publicize_ the whitelist - publicizing it would
mean listing it on http://sourceware.cygnus.com/lists.html or in
the bounce message or places like that.
3. I don't have a strong opinion one way or the other about
mentioning the whitelist on
http://sourceware.cygnus.com/sourceware/spam.html - I predict that
if we did mention it there, few non-sourceware-admins would find
it (there is a whole category of "non-publicized, but non-secret"
information as I found when running Cyclic).
4. It will be up to those project leaders who want to bother,
generally speaking, to add whitelist entries. I don't
particularly plan on adding people in response to email to
sourcemaster and postmaster.
5. Therefore, it is up to the project leaders in question to take
primarily responsibility for doing things like purging obsolete
entries (we might want an explicit policy of expiring them after a
year or whatever). And in general keeping the job of maintaining
it manageable (I predict that "If you make an exception for one,
you'll have to make exceptions for everyone" won't be a big
problem, although time will of course tell).
If people have further feedback on this subject, I'm sure I/we will
hear about it :-).
WARNING: multiple messages have this Message-ID
From: Jim Kingdon <kingdon@redhat.com>
To: cgf@cygnus.com
Cc: jlarmour@redhat.co.uk, overseers@sourceware.cygnus.com
Subject: Re: ORBS redux, round n
Date: Fri, 24 Mar 2000 09:54:00 -0000 [thread overview]
Message-ID: <200003241754.MAA23805@devserv.devel.redhat.com> (raw)
Message-ID: <20000324095400.h1ABZRKRxWxddnMF8gmhL1yjpK4_9dYIxeGkuSopiVE@z> (raw)
In-Reply-To: <20000324120154.A3986@cygnus.com>
1. I have added Chris Faylor and Jonathan Larmour to the sourceware
group. Don't upload trojan horses. Be careful. Buy low, sell high.
2. I don't plan to _publicize_ the whitelist - publicizing it would
mean listing it on http://sourceware.cygnus.com/lists.html or in
the bounce message or places like that.
3. I don't have a strong opinion one way or the other about
mentioning the whitelist on
http://sourceware.cygnus.com/sourceware/spam.html - I predict that
if we did mention it there, few non-sourceware-admins would find
it (there is a whole category of "non-publicized, but non-secret"
information as I found when running Cyclic).
4. It will be up to those project leaders who want to bother,
generally speaking, to add whitelist entries. I don't
particularly plan on adding people in response to email to
sourcemaster and postmaster.
5. Therefore, it is up to the project leaders in question to take
primarily responsibility for doing things like purging obsolete
entries (we might want an explicit policy of expiring them after a
year or whatever). And in general keeping the job of maintaining
it manageable (I predict that "If you make an exception for one,
you'll have to make exceptions for everyone" won't be a big
problem, although time will of course tell).
If people have further feedback on this subject, I'm sure I/we will
hear about it :-).
next prev parent reply other threads:[~2000-12-30 6:08 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-30 6:08 Jim Kingdon
2000-03-24 8:22 ` Jim Kingdon
2000-12-30 6:08 ` Chris Faylor
2000-03-24 8:28 ` Chris Faylor
2000-12-30 6:08 ` Jonathan Larmour
2000-03-24 8:32 ` Jonathan Larmour
2000-12-30 6:08 ` Chris Faylor
2000-03-24 8:33 ` Chris Faylor
2000-12-30 6:08 ` Jim Kingdon
2000-03-24 8:41 ` Jim Kingdon
2000-12-30 6:08 ` Tom Tromey
2000-03-24 8:50 ` Tom Tromey
2000-12-30 6:08 ` Chris Faylor
2000-03-24 8:53 ` Chris Faylor
2000-12-30 6:08 ` Jonathan Larmour
2000-03-24 8:54 ` Jonathan Larmour
2000-12-30 6:08 ` Jeffrey A Law
2000-03-24 9:19 ` Jeffrey A Law
2000-12-30 6:08 ` Jonathan Larmour
2000-03-24 9:22 ` Jonathan Larmour
2000-12-30 6:08 ` Chris Faylor
2000-03-24 9:57 ` Chris Faylor
2000-12-30 6:08 ` Chris Faylor
2000-03-24 8:58 ` Chris Faylor
2000-12-30 6:08 ` Chris Faylor
2000-03-24 9:02 ` Chris Faylor
2000-12-30 6:08 ` Jim Kingdon [this message]
2000-03-24 9:54 ` Jim Kingdon
2000-12-30 6:08 ` Jeffrey A Law
2000-03-24 9:11 ` Jeffrey A Law
2000-12-30 6:08 Phil Edwards
2000-03-24 9:04 ` Phil Edwards
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=200003241754.MAA23805@devserv.devel.redhat.com \
--to=kingdon@redhat.com \
--cc=cgf@cygnus.com \
--cc=jlarmour@redhat.co.uk \
--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).