public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Joseph Myers <jsm28@cam.ac.uk>
To: gcc-gnats@gcc.gnu.org
Cc: jsm28@cam.ac.uk
Subject: ada/6399: Inappropriate ACT references in gnat_rm
Date: Sun, 21 Apr 2002 13:46:00 -0000 [thread overview]
Message-ID: <E16zOAl-0001sl-00@jsm28.trin.cam.ac.uk> (raw)
>Number: 6399
>Category: ada
>Synopsis: Inappropriate ACT references in gnat_rm
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: doc-bug
>Submitter-Id: net
>Arrival-Date: Sun Apr 21 13:46:02 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator: Joseph S. Myers
>Release: 3.2 20020421 (experimental)
>Organization:
none
>Environment:
System: Linux digraph 2.2.20 #2 Sat Nov 10 16:44:22 UTC 2001 i686 unknown
Architecture: i686
host: i686-pc-linux-gnu
build: i686-pc-linux-gnu
target: i686-pc-linux-gnu
configured with: ../gcc-cvs/configure --prefix=/opt/gcc/mainline --disable-shared --enable-threads=posix --with-system-zlib
>Description:
The gnat_rm manual contains the following inappropriate reference to
Ada Core Technologies:
Ada Core
Technologies does not currently supply a suitable binding generator tool.
What some company called Ada Core Technologies does or does not supply
is irrelevant to and inappropriate in an FSF manual.
The other such references have already been removed from the mainline
manual. However, several more remain in the manual on the 3.1 branch
(some like this, some "For information on GLADE, contact Ada Core
Technologies."); the references on the branch should also be removed.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2002-04-21 20:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-21 13:46 Joseph Myers [this message]
2003-03-29 11:43 gerald
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=E16zOAl-0001sl-00@jsm28.trin.cam.ac.uk \
--to=jsm28@cam.ac.uk \
--cc=gcc-gnats@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).