public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/99884] Double spaces in warning message Date: Thu, 17 Nov 2022 19:41:29 +0000 [thread overview] Message-ID: <bug-99884-4-uRvY08GwUc@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99884-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99884 --- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Bernhard Reutner-Fischer <aldot@gcc.gnu.org>: https://gcc.gnu.org/g:19be89d79ee149e812ccc6027956cefb7f3e1016 commit r13-4133-g19be89d79ee149e812ccc6027956cefb7f3e1016 Author: Bernhard Reutner-Fischer <aldot@gcc.gnu.org> Date: Sun Oct 31 13:57:46 2021 +0100 Fortran: Remove double spaces in open() warning [PR99884] gcc/fortran/ChangeLog: PR fortran/99884 * io.cc (check_open_constraints): Remove double spaces.
prev parent reply other threads:[~2022-11-17 19:41 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-02 17:55 [Bug fortran/99884] New: " goeran at uddeborg dot se 2021-10-31 17:35 ` [Bug fortran/99884] " aldot at gcc dot gnu.org 2022-11-17 19:41 ` cvs-commit at gcc dot gnu.org [this message]
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-99884-4-uRvY08GwUc@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: linkBe 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).