From: Roland McGrath <roland@redhat.com>
To: overseers@sources.redhat.com
Cc: "Carlos O'Donell" <carlos@systemhalted.org>,
"Ryan S. Arnold" <rsa@us.ibm.com>
Subject: libc-help mailing list
Date: Mon, 21 Apr 2008 23:58:00 -0000 [thread overview]
Message-ID: <20080421235753.28BB927037B@magilla.localdomain> (raw)
There was supposed to be a libc-help mailing list created some several
weeks ago. The /ml/libc-help/ web page exists with empty archives.
But I get a "user unknown" bounce when I try to post to the list.
Frank couldn't figure it out.
At the same time, libc-alpha's settings were to be changed as discussed
before. We'd still like to happen once the libc-help list works properly.
But just the new list would be a fine start, and I am mystified as to how
it could fail to be a one-minute push-button operation.
Thanks,
Roland
next reply other threads:[~2008-04-21 23:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-21 23:58 Roland McGrath [this message]
2008-04-22 14:59 ` Christopher Faylor
2008-04-23 15:48 ` Ryan S. Arnold
2008-04-23 17:52 ` Christopher Faylor
2008-04-24 17:21 ` Joseph S. Myers
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=20080421235753.28BB927037B@magilla.localdomain \
--to=roland@redhat.com \
--cc=carlos@systemhalted.org \
--cc=overseers@sources.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).