public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Michael Meissner <meissner@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc(refs/users/meissner/heads/work084)] Update ChangeLog.meissner.
Date: Thu, 31 Mar 2022 14:01:08 +0000 (GMT)	[thread overview]
Message-ID: <20220331140108.833093898C71@sourceware.org> (raw)

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

commit b3657557ead4e256255c25efba6478775dd77093
Author: Michael Meissner <meissner@linux.ibm.com>
Date:   Wed Mar 30 14:00:50 2022 -0400

    Update ChangeLog.meissner.
    
    2022-03-30   Michael Meissner  <meissner@linux.ibm.com>
    
    gcc/
            * ChangeLog.meissner: Update.

Diff:
---
 gcc/ChangeLog.meissner | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/ChangeLog.meissner b/gcc/ChangeLog.meissner
index f646c26cfe5..dbe5df13eec 100644
--- a/gcc/ChangeLog.meissner
+++ b/gcc/ChangeLog.meissner
@@ -69,7 +69,7 @@ the regression tests.  There were no regressions in the runs:
 Can I install this into the trunk?  After a burn-in period, can I backport
 and install this into GCC 11 and GCC 10 branches?
 
-2022-03-29   Michael Meissner  <meissner@linux.ibm.com>
+2022-03-30   Michael Meissner  <meissner@linux.ibm.com>
 
 gcc/
 	PR target/99293


             reply	other threads:[~2022-03-31 14:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-31 14:01 Michael Meissner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-04-05 18:46 Michael Meissner
2022-04-02  0:50 Michael Meissner
2022-04-01 22:19 Michael Meissner
2022-03-31 19:55 Michael Meissner
2022-03-31 16:34 Michael Meissner
2022-03-31 14:00 Michael Meissner
2022-03-31 14:00 Michael Meissner
2022-03-31 14:00 Michael Meissner
2022-03-30 18:01 Michael Meissner
2022-03-29 23:57 Michael Meissner
2022-03-29  3:06 Michael Meissner
2022-03-29  0:12 Michael Meissner

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=20220331140108.833093898C71@sourceware.org \
    --to=meissner@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).