public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jerry DeLisle <jvdelisle@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-5234] Fix bug number reference in Changelogs
Date: Wed, 18 Jan 2023 01:31:44 +0000 (GMT)	[thread overview]
Message-ID: <20230118013144.F26D83858D28@sourceware.org> (raw)

https://gcc.gnu.org/g:04d7cc165387d19e1433a4b2157d2bde7b95305b

commit r13-5234-g04d7cc165387d19e1433a4b2157d2bde7b95305b
Author: Jerry DeLisle <jvdelisle@gcc.gnu.org>
Date:   Tue Jan 17 17:30:49 2023 -0800

    Fix bug number reference in Changelogs

Diff:
---
 gcc/fortran/ChangeLog-2022   | 2 +-
 gcc/testsuite/ChangeLog-2022 | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/gcc/fortran/ChangeLog-2022 b/gcc/fortran/ChangeLog-2022
index 71e551d9109..253af76c872 100644
--- a/gcc/fortran/ChangeLog-2022
+++ b/gcc/fortran/ChangeLog-2022
@@ -1,6 +1,6 @@
 2022-12-30  Steve Kargl  <kargl@gcc.gnu.org>
 
-	PR fortran/102595
+	PR fortran/102331
 	* decl.cc (attr_decl1): Guard against NULL pointer.
 	* parse.cc (match_deferred_characteristics): Include BT_CLASS in check for
 	derived being undefined.
diff --git a/gcc/testsuite/ChangeLog-2022 b/gcc/testsuite/ChangeLog-2022
index d9fafccda63..97827840cd1 100644
--- a/gcc/testsuite/ChangeLog-2022
+++ b/gcc/testsuite/ChangeLog-2022
@@ -11,7 +11,7 @@
 
 2022-12-30  Steve Kargl  <kargl@gcc.gnu.org>
 
-	PR fortran/102595
+	PR fortran/102331
 	* gfortran.dg/class_result_4.f90: Update error message check.
 	* gfortran.dg/pr85779_3.f90: Update error message check.

                 reply	other threads:[~2023-01-18  1:31 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20230118013144.F26D83858D28@sourceware.org \
    --to=jvdelisle@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).