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/dmf008)] Update ChangeLog.meissner
Date: Fri,  3 Feb 2023 19:30:25 +0000 (GMT)	[thread overview]
Message-ID: <20230203193025.63C6D3858C52@sourceware.org> (raw)

https://gcc.gnu.org/g:3db451715782f9156745bd8770c5d279ade46080

commit 3db451715782f9156745bd8770c5d279ade46080
Author: Michael Meissner <meissner@linux.ibm.com>
Date:   Fri Feb 3 14:30:22 2023 -0500

    Update ChangeLog.meissner

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

diff --git a/gcc/ChangeLog.meissner b/gcc/ChangeLog.meissner
index 38e30729cda..8dc1ea10078 100644
--- a/gcc/ChangeLog.meissner
+++ b/gcc/ChangeLog.meissner
@@ -17,7 +17,7 @@ the tradiational IBM double double format.  Assuming the other 6 patches for
 -mcpu=future are checked in (or at least the first patch), can I check this
 patch into the master branch for GCC 13.
 
-2023-02-02   Michael Meissner  <meissner@linux.ibm.com>
+2023-02-03   Michael Meissner  <meissner@linux.ibm.com>
 
 gcc/
 
@@ -75,7 +75,7 @@ the tradiational IBM double double format.  Assuming the other 6 patches for
 -mcpu=future are checked in (or at least the first patch), can I check this
 patch into the master branch for GCC 13?
 
-2023-02-02   Michael Meissner  <meissner@linux.ibm.com>
+2023-02-03   Michael Meissner  <meissner@linux.ibm.com>
 
 gcc/

             reply	other threads:[~2023-02-03 19:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-03 19:30 Michael Meissner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-02-02 20:39 Michael Meissner
2023-02-02 20:31 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=20230203193025.63C6D3858C52@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).