From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/gcc-patches:master commit in: 11.3.0/gentoo/
Date: Sat, 8 Jan 2022 04:09:11 +0000 (UTC) [thread overview]
Message-ID: <1641614914.3c8a43b56a2b4fdc040055dadb76665ad4fe0a9c.sam@gentoo> (raw)
commit: 3c8a43b56a2b4fdc040055dadb76665ad4fe0a9c
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sat Jan 8 04:08:34 2022 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sat Jan 8 04:08:34 2022 +0000
URL: https://gitweb.gentoo.org/proj/gcc-patches.git/commit/?id=3c8a43b5
11.3.0: cut patchset 4
Just includes the PCH fix.
Bug: https://bugs.gentoo.org/822690
Signed-off-by: Sam James <sam <AT> gentoo.org>
11.3.0/gentoo/README.history | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/11.3.0/gentoo/README.history b/11.3.0/gentoo/README.history
index bb83275..850c02b 100644
--- a/11.3.0/gentoo/README.history
+++ b/11.3.0/gentoo/README.history
@@ -1,4 +1,7 @@
-3 8 January 2022
+4 8 January 2022
+ + 76_all_all_PR103910_12_ICE-on-PCH.patch
+
+3 28 December 2021
U 26_all_enable-cet.patch
2 18 December 2021
next reply other threads:[~2022-01-08 4:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-08 4:09 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-08-22 2:14 [gentoo-commits] proj/gcc-patches:master commit in: 11.3.0/gentoo/ Sam James
2022-08-22 1:41 Sam James
2022-08-22 1:41 Sam James
2022-08-18 20:03 Sam James
2022-01-08 3:49 Sam James
2022-01-08 3:49 Sam James
2021-12-28 5:57 Sam James
2021-12-18 22:00 Sam James
2021-12-18 22:00 Sam James
2021-12-18 22:00 Sam James
2021-12-07 20:06 Sam James
2021-12-02 15:03 David Seifert
2021-12-02 15:03 David Seifert
2021-12-02 15:03 David Seifert
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=1641614914.3c8a43b56a2b4fdc040055dadb76665ad4fe0a9c.sam@gentoo \
--to=sam@gentoo.org \
--cc=gentoo-commits@lists.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