From: "Andrew Pinski" <pinskia@gmail.com>
To: "Ulrich Drepper" <drepper@redhat.com>
Cc: overseers@sourceware.org, "Roland McGrath" <roland@redhat.com>,
"Daniel Jacobowitz" <drow@false.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: Fri, 15 Feb 2008 18:48:00 -0000 [thread overview]
Message-ID: <de8d50360802151041y7f512f1eg622687331cbefd7d@mail.gmail.com> (raw)
In-Reply-To: <47B5AD93.7000304@redhat.com>
On 2/15/08, Ulrich Drepper <drepper@redhat.com> wrote:
> libc-hcker is not moderated. It's closed to non-subscribers. Big
> difference.
And this is the whole issue why have a closed list for an free source
project, that just seems wrong.
> No. libc-hacker is for the people doing the actual work. libc-alpha is
> for feedback on the current development code by other people.
This attitude is why some folks don't contribute at all to glibc.
What is actual work because I see so many more patches on libc-alpha
than libc-hacker.
-- Pinski
next prev parent reply other threads:[~2008-02-15 18:41 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 [this message]
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
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=de8d50360802151041y7f512f1eg622687331cbefd7d@mail.gmail.com \
--to=pinskia@gmail.com \
--cc=carlos@codesourcery.com \
--cc=drepper@redhat.com \
--cc=drow@false.org \
--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).