From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] glibc-2.16.0 stabilization train
Date: Thu, 25 Apr 2013 15:12:31 -0400 [thread overview]
Message-ID: <201304251512.32626.vapier@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 293 bytes --]
i've opened http://bugs.gentoo.org/467256 to track glibc-2.16 stabilization.
with the 2.18 release process starting up in a month or so, we need to make
room for it now that 2.17 is in ~arch. that means 2.16 going into arch since
it isn't realistically seeing anymore testing.
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
reply other threads:[~2013-04-25 19: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=201304251512.32626.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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