From: Ulrich Drepper <drepper@redhat.com>
To: GNU libc hacker <libc-hacker@sources.redhat.com>
Subject: glibc 2.5 on Sep 29
Date: Wed, 20 Sep 2006 17:12:00 -0000 [thread overview]
Message-ID: <4511767F.4040008@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 260 bytes --]
glibc 2.5 will be released on Sep 29. Just an advance warning. I'll
make no test releases, every Fedora rawhide build qualifies as that and
is much more effective.
--
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 251 bytes --]
next reply other threads:[~2006-09-20 17:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-20 17:12 Ulrich Drepper [this message]
2006-09-20 19:34 ` Steven Munroe
2006-09-20 19:53 ` Ulrich Drepper
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=4511767F.4040008@redhat.com \
--to=drepper@redhat.com \
--cc=libc-hacker@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).