From: "Carlos O'Donell" <carlos@systemhalted.org>
To: libc-alpha@sources.redhat.com, libc-announce@sources.redhat.com
Subject: New mailing list "libc-help" is active.
Date: Sat, 26 Apr 2008 17:12:00 -0000 [thread overview]
Message-ID: <119aab440804261004s418e17el3f9490bbc0626571@mail.gmail.com> (raw)
The GLIBC project has a new mailing list "libc-help" which is now active.
The libc-help list is intended for all glibc questions including build
problems, C library usage, and more. No question about glibc is ever
wrong on this list.
You may use the updated website to subscribe:
http://sources.redhat.com/glibc/
Cheers,
Carlos O'Donell
reply other threads:[~2008-04-26 17:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=119aab440804261004s418e17el3f9490bbc0626571@mail.gmail.com \
--to=carlos@systemhalted.org \
--cc=libc-alpha@sources.redhat.com \
--cc=libc-announce@sources.redhat.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).