From: Geert Bosch <bosch@gnat.com>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: Robert Dewar <dewar@gnat.com>,
"Joseph S. Myers" <jsm28@cam.ac.uk>,
gcc-patches@gcc.gnu.org
Subject: Re: ada/8560, [3.2], mainline: GNAT 3.14p is now required
Date: Sat, 16 Nov 2002 18:28:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.10.10211162120550.8122-100000@nile.gnat.com> (raw)
In-Reply-To: <87smy1906j.fsf@deneb.enyo.de>
On Sat, 16 Nov 2002, Florian Weimer wrote:
As far as I can tell, no such binaries have been released. I believe
that in the current state of the FSF GNAT sources, ACT doesn't want to
be too closely associated with them. *sigh*
This is not true. The main force to remove any mention of ACT from the
code and documentation came from others, including Joseph.
I will see what the situation is with the binaries at libre.act-europe.fr.
-Geert
next prev parent reply other threads:[~2002-11-17 2:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-16 3:03 Florian Weimer
2002-11-16 4:16 ` Joseph S. Myers
2002-11-16 4:19 ` Florian Weimer
2002-11-16 18:28 ` Geert Bosch [this message]
2002-11-17 0:34 ` Florian Weimer
2002-11-17 7:30 Geert Bosch
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=Pine.GSO.4.10.10211162120550.8122-100000@nile.gnat.com \
--to=bosch@gnat.com \
--cc=dewar@gnat.com \
--cc=fw@deneb.enyo.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=jsm28@cam.ac.uk \
/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).