public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: Ulrich Drepper <drepper@redhat.com>,
	Roland McGrath <roland@redhat.com>,
	overseers@sourceware.org, "Ryan S. Arnold" <rsa@us.ibm.com>,
	Carlos O'Donell <carlos@codesourcery.com>
Subject: Re: Create a libc-help mailing list for the GNU Libc project.
Date: Tue, 26 Feb 2008 23:02:00 -0000	[thread overview]
Message-ID: <20080226142034.GA882@ednor.casa.cgf.cx> (raw)
In-Reply-To: <1203997807.20040.1.camel@localhost>

On Mon, Feb 25, 2008 at 09:50:07PM -0600, Ryan S. Arnold wrote:
>On Mon, 2008-02-25 at 19:28 -0800, Roland McGrath wrote:
>> Ulrich does not want to see the libc-alpha moderation queue.  Ryan and
>> Carlos will be the moderators, and only they want to see this queue.
>> We will let you know if we have more people collaborating on the
>> moderators' work.  
>> 
>> My guess is that most likely it would be fine for subscribers not to
>> have their posts moderated.  But since libc-alpha subscription has
>> AFAIK not been selective, perhaps that is not so.  I will holding Ryan
>> and Carlos accountable for the manifest quality of the traffic that
>> gets through and the timeliness of the moderation process, and I'm
>> glad to delegate the decisions on how best to optimize those metrics
>> to those who have volunteered to keep them high.
>
>If the mailing list interface is anything like others I have used Carlos
>and I can blanket accept posts from certain developers.  Hopefully we
>can live up to the expectations.

We use ezmlm:  http://sourceware.org/lists.html#what-software .

AFAIK, there is nothing like a "blanket accept".  However, you might
want to research what is available.

cgf

  reply	other threads:[~2008-02-26 14:21 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-14 21:35 Carlos O'Donell
2008-02-14 23:46 ` Christopher Faylor
2008-02-14 23:55   ` Roland McGrath
2008-02-14 23:59     ` Christopher Faylor
2008-02-15  1:58       ` Roland McGrath
2008-02-15  5:04       ` Andrew Pinski
2008-02-15 10:53         ` Ryan S. Arnold
2008-02-15 15:00           ` Andrew Pinski
2008-02-15 15:06             ` Christopher Faylor
2008-02-15 15:12               ` Daniel Jacobowitz
2008-02-15 15:17                 ` Christopher Faylor
2008-02-15 15:25                   ` Carlos O'Donell
2008-02-15 18:41                   ` Ulrich Drepper
2008-02-15 18:48                     ` Andrew Pinski
2008-02-15 15:25               ` Ulrich Drepper
2008-02-20 17:28                 ` Christopher Faylor
2008-02-24 21:07                   ` Christopher Faylor
2008-02-25  3:01                     ` Ryan S. Arnold
2008-02-25  5:19                       ` Christopher Faylor
2008-02-25 21:24                         ` Christopher Faylor
2008-02-26  3:50                           ` Roland McGrath
2008-02-26 14:21                             ` Ryan S. Arnold
2008-02-26 23:02                               ` Christopher Faylor [this message]
2008-03-25  2:21                           ` Carlos O'Donell

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=20080226142034.GA882@ednor.casa.cgf.cx \
    --to=cgf-use-the-mailinglist-please@sourceware.org \
    --cc=carlos@codesourcery.com \
    --cc=drepper@redhat.com \
    --cc=overseers@sourceware.org \
    --cc=roland@redhat.com \
    --cc=rsa@us.ibm.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).