Mailing Lists

The libc-alpha and libc-help mailing lists are run by the ezmlm-idx mailing list software:

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

Mailing List Mission

libc-alpha - Ask/Answer technical questions regarding GLIBC development (i.e. spec interpretation, bugs, performance considerations, API issues, ABI issues, etc), Post patches for suggested fixes/enhancements that meet the contribution criteria.
libc-help - Ask/Answer questions regarding GLIBC development process, Ask/Answer question about building GLIBC, Post patches that aren't ready for contribution.

Moderation Mission

The libc-alpha mailing list is moderated by the GLIBC mailing list moderation team. We will do our best to moderate and allow appropriate emails to the libc-alpha mailing list. Our mission is as follows:

Re-direct GLIBC build questions to libc-help
Re-direct beginner developer questions to libc-help
Re-direct GLIBC usage questions to libc-help
Filter bug reports to bugzilla creation
Dispose of SPAM

Moderators

Ryan S. Arnold (rsa, ryanarn)
Carlos O'Donell (carlos)

Rejection Templates

Off Topic

%%%
Hi,

Please resend this email to the libc-help mailing list.  The libc-alpha mailing list is only for GLIBC development related comments, patches, and questions.  Questions regarding building or using GLIBC are outside of the scope of libc-alpha.

Regards,
libc-alpha moderation staff
%%%

Missing ChangeLog

%%%
Hi,

Your ChangeLog is missing.  Please resend this email to the libc-help mailing list for help writing a ChangeLog.  You can also follow the contribution checklist for information on formulating a correct ChangeLog:

http://sources.redhat.com/glibc/wiki/Contribution%20checklist

Regards,
libc-alpha moderation staff
%%%

Malformed ChangeLog

%%%
Hi,

Your ChangeLog is malformed.  Please resend this email to the libc-help mailing list for help in properly formatting a ChangeLog.  You can also follow the contribution checklist for information on formulating a correct ChangeLog:

http://sources.redhat.com/glibc/wiki/Contribution%20checklist

Regards,
libc-alpha moderation staff
%%%

Website Updates

%%%
Hi,

Questions regarding the GLIBC sourceware website or the GNU LIBC website should be directed to the libc-help mailing list.  The libc-alpha mailing list is only for GLIBC development related comments, patches, and questions.  

Regards,
libc-alpha moderation staff
%%%

Don't converse with the moderator

%%%
Hi,

Please don't converse with the moderator.  If you need help with your libc-alpha submission please use libc-help.

Emails to libc-alpha should only be those intended for consumption by all subscribers or emails contesting a moderation rejection.

Regards,
libc-alpha moderation staff
%%%

Build Errors

%%%
Hi,

GLIBC configuration or build failures should be reported to the libc-help mailing list.  While it is certainly possible that there is a build breakage due to a recent patch, the majority of all build failures are due to incorrect or inappropriate GLIBC configuration.  If there is a real problem the libc-help mailing list can help identify a fix that can then be brought to the libc-alpha mailing list.    The libc-alpha mailing list is only for GLIBC development related comments, patches, and questions.  

Regards,
libc-alpha moderation staff
%%%

Feature/Enhancement Requests

%%%
Hi,

For feature/enhancement requests please file a GLIBC enhancement bugzilla at http://sources.redhat.com/bugzilla/.  Then email the libc-help mailing list to begin formulating an appropriate enhancement request and include the link to the bugzilla entry.  Following this, a fully baked enhancement request can be sent to the libc-alpha mailing list.

Regards,
libc-alpha moderation staff
%%%