From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/gcc-patches:master commit in: 12.2.0/gentoo/
Date: Mon, 5 Dec 2022 00:27:27 +0000 (UTC) [thread overview]
Message-ID: <1670199836.98c1d96dbf03d704e546810c9fa14fe8edc402c2.sam@gentoo> (raw)
commit: 98c1d96dbf03d704e546810c9fa14fe8edc402c2
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Mon Dec 5 00:23:56 2022 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon Dec 5 00:23:56 2022 +0000
URL: https://gitweb.gentoo.org/proj/gcc-patches.git/commit/?id=98c1d96d
12.2.0: cut patchset 3
Signed-off-by: Sam James <sam <AT> gentoo.org>
12.2.0/gentoo/README.history | 1 +
1 file changed, 1 insertion(+)
diff --git a/12.2.0/gentoo/README.history b/12.2.0/gentoo/README.history
index a78f0e3..f1a7d9c 100644
--- a/12.2.0/gentoo/README.history
+++ b/12.2.0/gentoo/README.history
@@ -1,3 +1,4 @@
+3 5 Dec 2022
- 23_all_EXTRA_OPTIONS-z-now.patch
+ 23_all_DEF_GENTOO_ZNOW-z-now.patch
- 24_all_EXTRA_OPTIONS-fstack-clash-protection.patch
next reply other threads:[~2022-12-05 0:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 0:27 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-23 2:41 [gentoo-commits] proj/gcc-patches:master commit in: 12.2.0/gentoo/ Sam James
2023-03-13 22:28 Sam James
2023-02-12 2:39 Sam James
2023-02-06 18:36 Sam James
2023-02-06 17:40 Sam James
2023-01-29 8:50 Sam James
2023-01-23 0:35 Sam James
2023-01-08 4:46 Sam James
2022-12-28 19:35 Sam James
2022-12-26 8:06 Sam James
2022-12-17 4:54 Sam James
2022-12-09 11:24 Sam James
2022-12-05 0:18 Andreas K. Hüttel
2022-11-20 0:25 Sam James
2022-08-22 1:41 Sam James
2022-08-22 1:41 Sam James
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=1670199836.98c1d96dbf03d704e546810c9fa14fe8edc402c2.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