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>,
	Andrew Pinski <pinskia@gmail.com>,
	Roland McGrath <roland@redhat.com>,
	overseers@sourceware.org, rsa@us.ibm.com,
	Carlos O'Donell <carlos@codesourcery.com>
Subject: Re: Create a libc-help mailing list for the GNU Libc project.
Date: Sun, 24 Feb 2008 21:07:00 -0000	[thread overview]
Message-ID: <20080223221657.GA24906@ednor.casa.cgf.cx> (raw)
In-Reply-To: <20080215184836.GA17691@ednor.casa.cgf.cx>

On Fri, Feb 15, 2008 at 01:48:36PM -0500, Christopher Faylor wrote:
>On Fri, Feb 15, 2008 at 07:10:13AM -0800, Ulrich Drepper wrote:
>>Christopher Faylor wrote:
>>> Are you referring to libc-hacker, Andrew?  If so, that sounds like a good
>>> question to me.  Maybe libc-alpha should just be retired?
>>
>>No.  libc-hacker is for the people doing the actual work.  libc-alpha is
>>for feedback on the current development code by other people.
>
>Ok.  I'm not going to second-guess project leaders.
>
>I'll try to get to this over the weekend.  Setting up a new mailing list
>is trivial but I can never remember how to switch an existing mailing
>list to moderated.
>
>Does anyone in overseers have a cookbook for this by any chance?

I almost have this ready to go but I have a question about the
moderation of libc-alpha.  As far as I can tell, being a moderator means
getting every message that will be sent to the mailing list so that it
can be approved.  I can add extra people but should I keep Ulrich in the
list too?

Ulrich do you want to even see these messages?  If not, I'll remove you
as a moderator.

cgf

  reply	other threads:[~2008-02-23 22:17 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 [this message]
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
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=20080223221657.GA24906@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=pinskia@gmail.com \
    --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).