From: Richard Stallman <rms@gnu.org>
Cc: fxcoudert@gmail.com, ams@gnu.org, fortran@gcc.gnu.org,
wt@atmos.colostate.edu, sgk@troutmask.apl.washington.edu,
emacs-devel@gnu.org
Subject: Re: gfortran error format (was: Re: Emacs and GFortran)
Date: Sat, 04 Nov 2006 01:38:10 -0500 [thread overview]
Message-ID: <E1GgFAQ-0003hb-Av@fencepost.gnu.org> (raw)
In-Reply-To: <20061103075450.GA2526@acclab.helsinki.fi> (message from Erik Edelmann on Fri, 3 Nov 2006 09:54:50 +0200)
We will, sooner or later. But there are 123 other bugs (enhancement
requests not counted) in Bugzilla for Gfortran right now. They need to
be fixed too. We see no reason to give higher priority to this bug
than to the others.
I understand you can't fix all bugs right away. Since I don't know
what those other bugs are, I have no opinion on their relative
priority. But that is not the crucial point.
The crucial point here is to give this bug a substantial positive
priority -- to acknowledge that this is "something we need to fix"
rather than "you users can fix it if you like". It doesn't have to be
highest priority, but it does have to be substantial and positive.
next prev parent reply other threads:[~2006-11-04 6:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-02 14:08 gfortran error format (was: Re: Emacs and GFortran) François-Xavier Coudert
2006-11-02 14:20 ` Alfred M. Szmidt
2006-11-02 15:40 ` Steve Kargl
2006-11-02 20:14 ` gfortran error format David Kastrup
2006-11-03 7:08 ` gfortran error format (was: Re: Emacs and GFortran) Richard Stallman
2006-11-03 7:54 ` Erik Edelmann
2006-11-03 9:06 ` François-Xavier Coudert
2006-11-04 6:38 ` Richard Stallman [this message]
2006-11-03 8:21 ` Brooks Moses
2006-11-03 14:14 ` gfortran error format Stefan Monnier
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=E1GgFAQ-0003hb-Av@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=ams@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=fortran@gcc.gnu.org \
--cc=fxcoudert@gmail.com \
--cc=sgk@troutmask.apl.washington.edu \
--cc=wt@atmos.colostate.edu \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.