public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jb at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/53796] I/O INQUIRE of RECL: If not specified in OPEN, the default value should be returned (sequential access)
Date: Tue, 20 Oct 2015 17:58:00 -0000 [thread overview]
Message-ID: <bug-53796-4-Wf0hKXdguA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53796-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53796
Janne Blomqvist <jb at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |NEW
--- Comment #15 from Janne Blomqvist <jb at gcc dot gnu.org> ---
AFAICT it remains unfixed. GFortran development resources being what they are,
not all bugs can be promptly fixed.
But what's the rush to close old unfixed bugs anyway? "Number of open bugs" is
a ridiculous metric for software quality, especially if one then closes
unfixed bugs in some kind of effort to boost said metric.
next prev parent reply other threads:[~2015-10-20 17:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-28 10:26 [Bug fortran/53796] New: " burnus at gcc dot gnu.org
2012-06-28 15:42 ` [Bug fortran/53796] " burnus at gcc dot gnu.org
2012-06-28 18:22 ` clivegpage at gmail dot com
2012-06-29 9:56 ` jvdelisle at gcc dot gnu.org
2012-06-29 10:00 ` clivegpage at gmail dot com
2012-06-29 10:07 ` burnus at gcc dot gnu.org
2012-06-29 10:13 ` jvdelisle at gcc dot gnu.org
2012-06-29 13:29 ` burnus at gcc dot gnu.org
2012-06-29 15:05 ` burnus at gcc dot gnu.org
2012-06-29 23:43 ` jvdelisle at gcc dot gnu.org
2012-06-30 0:32 ` jvdelisle at gcc dot gnu.org
2012-06-30 1:35 ` jvdelisle at gcc dot gnu.org
2012-06-30 8:40 ` clivegpage at gmail dot com
2012-06-30 20:10 ` jb at gcc dot gnu.org
2015-10-20 17:14 ` dominiq at lps dot ens.fr
2015-10-20 17:58 ` jb at gcc dot gnu.org [this message]
2015-10-20 18:57 ` dominiq at lps dot ens.fr
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-53796-4-Wf0hKXdguA@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).