public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Peter Bergner <bergner@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc(refs/vendors/ibm/heads/gcc-10-branch)] ibm: Merge up to top of releases/gcc-10
Date: Thu, 25 Jun 2020 00:35:40 +0000 (GMT)	[thread overview]
Message-ID: <20200625003540.8E51B398BC22@sourceware.org> (raw)

https://gcc.gnu.org/g:fa34f36ef5e9604b2645490003d7d750a3efc9c0

commit fa34f36ef5e9604b2645490003d7d750a3efc9c0
Author: Peter Bergner <bergner@linux.ibm.com>
Date:   Wed Jun 24 19:21:31 2020 -0500

    ibm: Merge up to top of releases/gcc-10
    
    2020-06-24  Peter Bergner  <bergner@linux.ibm.com>
    
            Merge up to releases/gcc-10 8e25bae517450c001f5e84b7ab24f06bb1425df6.

Diff:
---
 gcc/ChangeLog.ibm | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/gcc/ChangeLog.ibm b/gcc/ChangeLog.ibm
new file mode 100644
index 00000000000..8b810b09b30
--- /dev/null
+++ b/gcc/ChangeLog.ibm
@@ -0,0 +1,3 @@
+2020-06-24  Peter Bergner  <bergner@linux.ibm.com>
+
+	Merge up to releases/gcc-10 8e25bae517450c001f5e84b7ab24f06bb1425df6.


             reply	other threads:[~2020-06-25  0:35 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-25  0:35 Peter Bergner [this message]
2020-07-02 21:09 Peter Bergner
2020-07-03  3:00 Peter Bergner
2020-07-23 19:06 Peter Bergner
2020-07-30 16:58 Peter Bergner
2020-08-19 14:02 Peter Bergner
2020-09-03 16:41 Peter Bergner
2020-09-15 16:44 Peter Bergner
2020-09-15 19:09 Peter Bergner
2020-09-24 19:02 Peter Bergner
2021-01-04 22:27 Peter Bergner
2021-03-17 21:09 Peter Bergner
2021-04-12 18:59 Peter Bergner
2021-06-18 19:47 Peter Bergner
2021-09-22 13:24 Peter Bergner
2022-01-15  7:09 Peter Bergner
2022-02-18 23:33 Peter Bergner
2022-03-29 22:32 Peter Bergner
2022-08-24  0:43 Peter Bergner
2023-03-06 22:37 Peter Bergner
2023-08-01 19:33 Peter Bergner

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=20200625003540.8E51B398BC22@sourceware.org \
    --to=bergner@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).