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
%%%

Off Topic (libc-ports cross-posting)

%%%
Hi,

Discussions taking place on the libc-ports mailing list that don't directly impact platform generic GLIBC support are considered off-topic for the libc-alpha mailing list.

Regards,
libc-alpha moderation staff
%%%

Inlined ChangeLog

%%%
Hi,

You have modified the glibc ChangeLog file contrary to the guidelines outlined here:

http://sourceware.org/glibc/wiki/Contribution%20checklist

Please don't modify the ChangeLog file in the source code.  That is handled by the maintainer.  Remove your ChangeLog from the diff body and have it precede the diff as indicated in the aforementioned link and then resubmit to libc-alpha.  If you need help formulating a proper ChangeLog please email the libc-help mailing list.

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
%%%

Missing ChangeLog (libc-alpha cross-posting)

%%%
Hi,

Your ChangeLog is missing.  

Please include a ChangeLog even when cross-posting between glibc mailing lists if you CC libc-alpha.  You can find information on constructing a ChangeLog here:

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
%%%

Insufficient Analysis

%%%
Hi,

The issue that you are reporting may be a failure in GLIBC, but it is too light on details.  Please either re-post it to the libc-help mailing list for community discussion, or add further analysis to your next libc-alpha email.

Regards,
libc-alpha moderation staff
%%%

Feature/Enhancement Requests

%%%
Hi,

If you want to propose a new feature or enhancement in GLIBC but cannot prepare a patch yourself right away, please consult the libc-help mailing list first; we will help you decide whether such a feature is appropriate for GLIBC (frequently, problems are best addressed in other ways) and what would be the best way to address your original issue. Afterwards, the discussion may move to the libc-alpha mailing list in case implementation issues need to be addressed, or you can file an enhancement request in the GLIBC bugzilla at http://sources.redhat.com/bugzilla/ based on the feedback you have received.

Regards,
libc-alpha moderation staff
%%%

Wrong Mailing List - Locale

%%%
Hi,

Issues regarding locales should be sent to the libc-locale mailing list rather than libc-alpha.  Please resubmit your email there.  You can sign up for libc-locale at the following webpage.

http://sourceware.org/glibc/

Regards,
libc-alpha moderation staff
%%%