public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: ada/6919: Bug box refers to missing file gnatinfo.txt
Date: Mon, 03 Jun 2002 07:56:00 -0000	[thread overview]
Message-ID: <20020603145604.14670.qmail@sources.redhat.com> (raw)

The following reply was made to PR ada/6919; it has been noted by GNATS.

From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: <David.Billinghurst@riotinto.com>
Cc: <gcc-gnats@gcc.gnu.org>,  <gcc-bugs@gcc.gnu.org>
Subject: Re: ada/6919: Bug box refers to missing file gnatinfo.txt
Date: Mon, 3 Jun 2002 15:55:20 +0100 (BST)

 On 3 Jun 2002 David.Billinghurst@riotinto.com wrote:
 
 > The ada bug box (below) refers to file gnatinfo.txt, but
 > the file is not in CVS or generated by the build.
 
 This is effectively a duplication of ada/5856 - various changes to the Ada
 front end (such as the proper bug box version) have been applied only to
 the 3.1 branch and not to the mainline (this should never happen, except
 where there's doubt about the right way to fix a problem on the mainline
 and there's a high-priority PR open describing the issue that needs fixing
 on the mainline to avoid a regression).  Could the Ada maintainers please
 go through all patches to the Ada compiler that have been applied to the
 3.1 branch since it was created and make sure that they are also on the
 mainline?  I believe the relevant patches are (from the CVS logs of
 ada/ChangeLog):
 
 revision 1.197.2.11
 date: 2002/05/04 03:27:12;  author: bosch;  state: Exp;  lines: +259 -0
         * 1aexcept.adb, 1aexcept.ads, 41intnam.ads, 42intnam.ads,
 [...]
         xref_lib.ads, xsinfo.adb, xsnames.adb, xtreeprs.adb : Change
         Ada Core Technologies from maintainer to contributor.
 
 (but of course all files present on mainline must be fixed, not just those 
 that were on 3.1 branch)
 
 revision 1.197.2.9
 date: 2002/05/01 21:15:24;  author: bosch;  state: Exp;  lines: +4 -0
         * comperr.adb : Fix typo.
 revision 1.197.2.8
 date: 2002/05/01 19:57:06;  author: bosch;  state: Exp;  lines: +10 -0
         * bindgen.adb (Public_Version_Warning): Remove.
 
         * gnatvsn.ads : Change to match GCC 3.1 version.
 
         * comperr.adb : Change bug box, remove ACT-specific circuitry.
 
         * comperr.ads : Update comments to reflect changed bug message.
 
 (but I've since fixed the version strings to be of standard GCC format)
 
 revision 1.197.2.4
 date: 2002/04/21 06:59:35;  author: fw;  state: Exp;  lines: +5 -0
         * adaint.c (__gnat_tmp_name): Remove buffer overflow bug on
                 GNU/Linux.
 
 (but you shouldn't rely on this list - diff the ada directory between the 
 branchpoint and head of branch and check through all patches found).
 
 -- 
 Joseph S. Myers
 jsm28@cam.ac.uk
 


             reply	other threads:[~2002-06-03 14:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-03  7:56 Joseph S. Myers [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-06-03  6:26 David.Billinghurst

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=20020603145604.14670.qmail@sources.redhat.com \
    --to=jsm28@cam.ac.uk \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).