public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Dave Love <d.love@dl.ac.uk>
To: egcs@cygnus.com
Subject: g77 changes
Date: Thu, 13 Nov 1997 12:55:00 -0000	[thread overview]
Message-ID: <rzqd8k47bu0.fsf@djlvig.dl.ac.uk> (raw)
In-Reply-To: <199711112146.QAA18548@melange.gnu.org>

In addition to Craig's comments I realize `g77 -v' no longer does what
we expect (see the manual).

Talking of which, the g77 manual needs an overhaul before release.  I
haven't reviewed it carefully, but at least these things need
attention:
 * Version info
 * Bug reporting procedure and addresses (and other occurrences of
   gnu.ai.mit.edu)
 * Installation instructions
 * Bug fix and operational changes since 0.5.21 that aren't in
   burley's patches (like the changes under discussion, if they must
   persist)

[I'm particularly concerned about the first two, as a fortran@gnu
muggins and responder to random posts.]

  parent reply	other threads:[~1997-11-13 12:55 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-11-10 18:41 collect2 compiles C with g77 ! Philippe De Muyter
1997-11-11  3:35 ` Dave Love
1997-11-11  9:33   ` Jeffrey A Law
1997-11-11 13:51     ` Craig Burley
1997-11-12  6:25       ` Paul Koning
1997-11-13 12:55       ` Dave Love [this message]
1997-11-17 13:55         ` g77 changes Jeffrey A Law
1997-11-17 15:59           ` Craig Burley
1997-11-18 10:01             ` Dave Love
1997-11-18 23:53             ` Jeffrey A Law
1997-11-18  9:55           ` Dave Love
1997-11-18 23:53             ` Jeffrey A Law
1997-11-17 13:55       ` collect2 compiles C with g77 ! Jeffrey A Law
1997-11-25 19:56 ` Jeffrey A Law
1997-11-26 11:01   ` Craig Burley
     [not found] ` <16517.880498727.cygnus.egcs@cygnus.com>
1997-11-25 22:49   ` Jason Merrill
1997-11-26  0:57     ` Jeffrey A Law
1997-11-26  0:57       ` Jason Merrill

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=rzqd8k47bu0.fsf@djlvig.dl.ac.uk \
    --to=d.love@dl.ac.uk \
    --cc=egcs@cygnus.com \
    /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).