public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/105473] semicolon allowed when list-directed read integer with decimal='point'
Date: Fri, 06 May 2022 20:39:20 +0000 [thread overview]
Message-ID: <bug-105473-4-KWBfWlf6WL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105473-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105473
--- Comment #5 from anlauf at gcc dot gnu.org ---
(In reply to Jerry DeLisle from comment #4)
> I see I no longer have change status on PRs. Evidently some of the address
> and login changes I have had to do in the process of changing my email
> providers has messed it all up.
Jerry,
have you tried to log in using your @gcc.gnu.org address?
next prev parent reply other threads:[~2022-05-06 20:39 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 8:38 [Bug fortran/105473] New: " john.harper at vuw dot ac.nz
2022-05-05 2:14 ` [Bug fortran/105473] " jvdelisle2 at gmail dot com
2022-05-05 2:21 ` jvdelisle2 at gmail dot com
2022-05-05 2:50 ` harper at msor dot vuw.ac.nz
2022-05-06 1:26 ` jvdelisle2 at gmail dot com
2022-05-06 20:39 ` anlauf at gcc dot gnu.org [this message]
2022-05-08 14:54 ` jvdelisle at gcc dot gnu.org
2022-05-14 22:00 ` jvdelisle at gcc dot gnu.org
2022-05-15 8:59 ` harper at msor dot vuw.ac.nz
2022-05-15 14:37 ` jvdelisle at gcc dot gnu.org
2022-05-15 15:56 ` jvdelisle at gcc dot gnu.org
2022-05-16 0:10 ` harper at msor dot vuw.ac.nz
2022-05-16 0:42 ` jvdelisle at gcc dot gnu.org
2022-05-16 0:49 ` jvdelisle at gcc dot gnu.org
2022-05-16 0:55 ` jvdelisle at gcc dot gnu.org
2022-05-16 1:44 ` harper at msor dot vuw.ac.nz
2022-05-16 4:12 ` harper at msor dot vuw.ac.nz
2022-05-16 21:13 ` harper at msor dot vuw.ac.nz
2022-05-18 2:52 ` jvdelisle at gcc dot gnu.org
2022-05-19 0:10 ` harper at msor dot vuw.ac.nz
2022-06-03 4:33 ` jvdelisle at gcc dot gnu.org
2022-06-03 9:11 ` harper at msor dot vuw.ac.nz
2022-06-03 21:04 ` jvdelisle at gcc dot gnu.org
2022-06-04 3:47 ` harper at msor dot vuw.ac.nz
2022-07-02 17:14 ` jvdelisle at gcc dot gnu.org
2022-07-03 3:52 ` harper at msor dot vuw.ac.nz
2022-07-04 3:48 ` jvdelisle at gcc dot gnu.org
2024-02-17 18:04 ` cvs-commit at gcc dot gnu.org
2024-03-08 0:29 ` cvs-commit at gcc dot gnu.org
2024-03-08 0:30 ` jvdelisle at gcc dot gnu.org
2024-03-08 7:21 ` john.harper at vuw dot ac.nz
2024-03-09 19:12 ` jvdelisle at gcc dot gnu.org
2024-03-11 12:48 ` burnus at gcc dot gnu.org
2024-03-11 22:48 ` jvdelisle at gcc dot gnu.org
2024-03-14 8:40 ` burnus at gcc dot gnu.org
2024-03-14 9:16 ` burnus at gcc dot gnu.org
2024-04-03 3:36 ` jvdelisle at gcc dot gnu.org
2024-04-03 3:50 ` jvdelisle at gcc dot gnu.org
2024-04-06 13:56 ` cvs-commit at gcc dot gnu.org
2024-04-22 4:23 ` cvs-commit at gcc dot gnu.org
2024-04-22 4:25 ` jvdelisle at gcc dot gnu.org
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=bug-105473-4-KWBfWlf6WL@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).