From: Joe Buck <jbuck@synopsys.com>
To: law@cygnus.com
Cc: kriol@fnal.gov, egcs@cygnus.com
Subject: Re: Info discrepancy
Date: Tue, 02 Dec 1997 23:24:00 -0000 [thread overview]
Message-ID: <199712030651.WAA13990@atrus.synopsys.com> (raw)
In-Reply-To: <26490.881115527@cygnus.com>
> > bugs. It corresponds to GNU CC version 2.7.2.
> We do not want to go change ever reference to egcs; gcc2 is a component
> included in egcs -- thus most of the text is still relavent.
>
> One could argue the version # should change, but what should it change to?
If the manual is not the FSF version, it must not lie and say that
it is. So there has to be an egcs reference (unless the manual
is the same as the forthcoming 2.8.0 manual).
Possibilities:
It corresponds to GNU CC version egcs-1.0.
It corresponds to GNU CC version 2.8.0 (plus egcs features).
next prev parent reply other threads:[~1997-12-02 23:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-02 16:29 [cygnus.bug-gcc] `-Q' switch to GCC is not documented; fix included Michael Meissner
1997-12-02 12:16 ` Jeffrey A Law
1997-12-02 18:18 ` Info discrepancy Oleg Krivosheev
1997-12-02 18:18 ` Jeffrey A Law
1997-12-02 23:24 ` Joe Buck [this message]
1997-12-02 23:24 ` Jeffrey A Law
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=199712030651.WAA13990@atrus.synopsys.com \
--to=jbuck@synopsys.com \
--cc=egcs@cygnus.com \
--cc=kriol@fnal.gov \
--cc=law@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).