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/work154)] Update ChangeLog.*
Date: Tue, 23 Jan 2024 05:04:37 +0000 (GMT)	[thread overview]
Message-ID: <20240123050438.A00503858C50@sourceware.org> (raw)

https://gcc.gnu.org/g:3072378a3c6e4c320676293251a51d015e9f7d7b

commit 3072378a3c6e4c320676293251a51d015e9f7d7b
Author: Michael Meissner <meissner@linux.ibm.com>
Date:   Tue Jan 23 00:04:34 2024 -0500

    Update ChangeLog.*

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

diff --git a/gcc/ChangeLog.meissner b/gcc/ChangeLog.meissner
index eee6fe0c72a..eba680618fe 100644
--- a/gcc/ChangeLog.meissner
+++ b/gcc/ChangeLog.meissner
@@ -42,7 +42,7 @@ the trunk?
 It would be nice if I could apply it to the open branches.  Can I backport it
 after a burn-in period?
 
-2024-01-10  Michael Meissner  <meissner@linux.ibm.com>
+2024-01-23  Michael Meissner  <meissner@linux.ibm.com>
 
 gcc/
 
@@ -111,7 +111,7 @@ systems doing the normal bootstrap and test.  There were no regressions in any
 of the tests, and the new tests passed.  Can I check this patch into the master
 branch?
 
-2024-01-09  Michael Meissner  <meissner@linux.ibm.com>
+2024-01-23  Michael Meissner  <meissner@linux.ibm.com>
 
 gcc/
 
@@ -145,7 +145,7 @@ gcc/testsuite/
 
 Add ChangeLog.meissner and REVISION.
 
-2024-01-09  Michael Meissner  <meissner@linux.ibm.com>
+2024-01-23  Michael Meissner  <meissner@linux.ibm.com>
 
 gcc/

             reply	other threads:[~2024-01-23  5:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-23  5:04 Michael Meissner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-23  4:56 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=20240123050438.A00503858C50@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).