From: Sam James <sam@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: toolchain@gentoo.org
Subject: Re: [gentoo-dev] GCC 14 unleashed
Date: Sun, 19 May 2024 16:31:14 +0100 [thread overview]
Message-ID: <878r05lsxp.fsf@gentoo.org> (raw)
In-Reply-To: <87ed9xlvhj.fsf@gentoo.org> (Sam James's message of "Sun, 19 May 2024 15:36:08 +0100")
[-- Attachment #1: Type: text/plain, Size: 152 bytes --]
Sam James <sam@gentoo.org> writes:
Oh, and:
> * The code was broken before (badly) [...]
... and therefore you should be revbumping for fixes.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 377 bytes --]
prev parent reply other threads:[~2024-05-19 15:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-19 14:36 [gentoo-dev] GCC 14 unleashed Sam James
2024-05-19 15:31 ` Sam James [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=878r05lsxp.fsf@gentoo.org \
--to=sam@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=toolchain@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