public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/gcc] rhel-f41-base: 7.2.1-1
Date: Mon, 29 Jun 2026 12:27:36 GMT [thread overview]
Message-ID: <178273605664.1.8697776734536095441.rpms-gcc-ff60308ab957@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/gcc
Branch : rhel-f41-base
Commit : ff60308ab95743885d1bf4da3c2df3f32858155d
Author : Jakub Jelinek <jakub@redhat.com>
Date : 2017-08-30T17:06:21+02:00
Stats : +18/-6 in 2 file(s)
URL : https://src.fedoraproject.org/rpms/gcc/c/ff60308ab95743885d1bf4da3c2df3f32858155d?branch=rhel-f41-base
Log:
7.2.1-1
---
diff --git a/gcc.spec b/gcc.spec
index ceb2d0b..a16ffac 100644
--- a/gcc.spec
+++ b/gcc.spec
@@ -1,10 +1,10 @@
-%global DATE 20170802
-%global SVNREV 250834
-%global gcc_version 7.1.1
+%global DATE 20170829
+%global SVNREV 251415
+%global gcc_version 7.2.1
%global gcc_major 7
# Note, gcc_release must be integer, if you want to add suffixes to
# %{release}, append them after %{gcc_release} on Release: line.
-%global gcc_release 7
+%global gcc_release 1
%global nvptx_tools_gitrev c28050f60193b3b95a18866a96f03334e874e78f
%global nvptx_newlib_gitrev aadc8eb0ec43b7cd0dd2dfb484bae63c8b05ef24
%global _unpackaged_files_terminate_build 0
@@ -3238,6 +3238,18 @@ fi
%endif
%changelog
+* Tue Aug 29 2017 Jakub Jelinek <jakub@redhat.com> 7.2.1-1
+- update from the 7 branch
+ - 7.2 release
+ - PRs c++/67054, c++/81607, debug/81993, driver/81523, fortran/80164,
+ fortran/81296, ipa/77732, libstdc++/53984, libstdc++/79820,
+ libstdc++/81751, middle-end/81065, middle-end/81088, middle-end/81766,
+ middle-end/81884, sanitizer/80932, target/67712, target/72804,
+ target/78460, target/80210, target/81170, target/81295, target/81861,
+ target/81894, target/81910, target/81921, testsuite/81056,
+ tree-optimization/81181, tree-optimization/81354,
+ tree-optimization/81723, tree-optimization/81977
+
* Wed Aug 2 2017 Jakub Jelinek <jakub@redhat.com> 7.1.1-7
- update from the 7 branch
- 7.2-rc1
diff --git a/gcc7-libstdc++-docs.patch b/gcc7-libstdc++-docs.patch
index b9f63a3..125091b 100644
--- a/gcc7-libstdc++-docs.patch
+++ b/gcc7-libstdc++-docs.patch
@@ -4,7 +4,7 @@
<a class="link" href="http://www.fsf.org/" target="_top">FSF
</a>
</p><p>
-+ Release 7.1.1
++ Release 7.2.1
+ </p><p>
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation
@@ -17,7 +17,7 @@
</p><p>
- The API documentation, rendered into HTML, can be viewed online
+ The API documentation, rendered into HTML, can be viewed locally
-+ <a class="link" href="api/index.html" target="_top">for the 7.1.1 release</a>,
++ <a class="link" href="api/index.html" target="_top">for the 7.2.1 release</a>,
+ online
<a class="link" href="http://gcc.gnu.org/onlinedocs/" target="_top">for each GCC release</a>
and
next reply other threads:[~2026-06-29 12:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 12:27 Jakub Jelinek [this message]
2026-06-29 12:27 [rpms/gcc] rhel-f41-base: 7.2.1-1 Marek Polacek
2026-06-29 12:27 Marek Polacek
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=178273605664.1.8697776734536095441.rpms-gcc-ff60308ab957@fedoraproject.org \
--to=jakub@redhat.com \
--cc=git-commits@fedoraproject.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