public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Getting glibc-2.26 stable (reminder)
Date: Fri, 30 Mar 2018 19:45:07 +0200	[thread overview]
Message-ID: <6280002.e6JlcsyyTa@pinacolada> (raw)
In-Reply-To: <4728256.M3KvIINVCW@pinacolada>

[-- Attachment #1: Type: text/plain, Size: 516 bytes --]

Am Freitag, 30. März 2018, 19:15:16 CEST schrieb Andreas K. Huettel:
> 
> Hey all,
> 
> now that upstream has already released glibc-2.27, we should think about
> getting glibc-2.26 stable soon. That, however, means work for all of us.
> 

And, as this seems to be a frequently asked question: My plan is to re-add 
keywords to 2.27 once the stable request for 2.26 has arches in cc. 


-- 
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer
(council, toolchain, perl, libreoffice, comrel)

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 981 bytes --]

      reply	other threads:[~2018-03-30 17:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-30 17:15 [gentoo-dev] Getting glibc-2.26 stable (reminder) Andreas K. Huettel
2018-03-30 17:45 ` Andreas K. Huettel [this message]

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=6280002.e6JlcsyyTa@pinacolada \
    --to=dilfridge@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