From: Jeffrey A Law <law@cygnus.com>
To: Jim Kingdon <kingdon@redhat.com>
Cc: cgf@cygnus.com, 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: <20291.953917396@upchuck> (raw)
In-Reply-To: <200003241641.LAA18292@devserv.devel.redhat.com>
In message < 200003241641.LAA18292@devserv.devel.redhat.com >you write:
> >Or easier still, just a whitelist that individual project maintainers can
> >edit?
>
> That sounds like an excellent idea. It fits in nicely with my scheme
> to try to dump more work ^W^W^W get more help ^W^W^W empower the
> project maintainers. And it seems to make sense in the context of
> "anarchy" or whatever the right word is for our governance structure.
This can be done, it wouldn't be that tough.
Each list has a file "editor" which runs the various filters and
processes to get a message to the list. I believe the first line in
each looks something like:
|/usr/sourceware/bin/rbl-check.sh gcc-patches --gcc-list
By passing various arguments (and possibly extending that file) we can
use project specific whitelists.
jeff
WARNING: multiple messages have this Message-ID
From: Jeffrey A Law <law@cygnus.com>
To: Jim Kingdon <kingdon@redhat.com>
Cc: cgf@cygnus.com, jlarmour@redhat.co.uk, overseers@sourceware.cygnus.com
Subject: Re: ORBS redux, round n
Date: Fri, 24 Mar 2000 09:11:00 -0000 [thread overview]
Message-ID: <20291.953917396@upchuck> (raw)
Message-ID: <20000324091100.4j62Q1qUe3y_Cx9P_kimo1-kI3TC1wuKYs3i1Y9yv5U@z> (raw)
In-Reply-To: <200003241641.LAA18292@devserv.devel.redhat.com>
In message < 200003241641.LAA18292@devserv.devel.redhat.com >you write:
> >Or easier still, just a whitelist that individual project maintainers can
> >edit?
>
> That sounds like an excellent idea. It fits in nicely with my scheme
> to try to dump more work ^W^W^W get more help ^W^W^W empower the
> project maintainers. And it seems to make sense in the context of
> "anarchy" or whatever the right word is for our governance structure.
This can be done, it wouldn't be that tough.
Each list has a file "editor" which runs the various filters and
processes to get a message to the list. I believe the first line in
each looks something like:
|/usr/sourceware/bin/rbl-check.sh gcc-patches --gcc-list
By passing various arguments (and possibly extending that file) we can
use project specific whitelists.
jeff
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 ` Jeffrey A Law [this message]
2000-03-24 9:11 ` Jeffrey A Law
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
2000-03-24 9:54 ` 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 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=20291.953917396@upchuck \
--to=law@cygnus.com \
--cc=cgf@cygnus.com \
--cc=jlarmour@redhat.co.uk \
--cc=kingdon@redhat.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).