From: "Hanno Böck" <hanno@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] gcc-6.x status inquiry
Date: Wed, 3 May 2017 19:10:42 +0200 [thread overview]
Message-ID: <20170503191042.1fda0063@pc1> (raw)
In-Reply-To: <20170503164311.GA20929@whubbs1.gaikai.biz>
[-- Attachment #1: Type: text/plain, Size: 561 bytes --]
On Wed, 3 May 2017 11:43:11 -0500
William Hubbs <williamh@gentoo.org> wrote:
> I see that gcc-6.3 doesn't have keywords, so I'm
> wondering when it will get them? Does anyone have any idea? I'm not
> talking about stable keywords, just ~. ;-)
Given that gcc 7.1 was just released and gcc 6 isn't even keyworded yet
I'm wondering if it'd be an idea to right away strive for gcc 7 and
skip keywording+stabilizing gcc 6.x in gentoo.
--
Hanno Böck
https://hboeck.de/
mail/jabber: hanno@hboeck.de
GPG: FE73757FA60E4E21B937579FA5880072BBB51E42
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-05-03 17:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-03 16:43 [gentoo-dev] gcc-6.x status inquiry William Hubbs
2017-05-03 17:10 ` Hanno Böck [this message]
2017-05-03 17:58 ` [gentoo-dev] " Luca Barbato
2017-05-03 18:00 ` Ian Stakenvicius
2017-05-03 18:42 ` William Hubbs
2017-05-03 19:06 ` Ian Stakenvicius
2017-05-03 18:44 ` Erik Närström
2017-05-04 7:28 ` grozin
2017-05-04 7:48 ` Erik Närström
2017-05-03 18:57 ` [gentoo-dev] " Andreas K. Huettel
2017-05-03 19:25 ` Matthias Maier
2017-05-04 15:22 ` Thomas Deutschmann
2017-05-04 21:32 ` Getting gcc-6 keyworded (was: Re: [gentoo-dev] gcc-6.x status inquiry) Andreas K. Huettel
2017-05-04 21:33 ` Andreas K. Huettel
2017-05-04 21:20 ` [gentoo-dev] gcc-6.x status inquiry William Hubbs
2017-05-04 21:30 ` Matthias Maier
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=20170503191042.1fda0063@pc1 \
--to=hanno@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