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/6558: Wrongly reverted patches
Date: Sat, 04 May 2002 09:26:00 -0000	[thread overview]
Message-ID: <E1742EI-0005c9-00@jsm28.trin.cam.ac.uk> (raw)


>Number:         6558
>Category:       ada
>Synopsis:       Wrongly reverted patches
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat May 04 09:26:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Joseph S. Myers
>Release:        3.2 20020504 (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 big Ada merge (mainline only) wrongly reverted some patches that
had been made to the FSF GCC tree.  These need to be unreverted, and a
proper check made for whether any other patches were reverted that
shouldn't have been.

A list, which may be incomplete, is at
<URL:http://gcc.gnu.org/ml/gcc-patches/2002-03/msg00402.html>.

>How-To-Repeat:

>Fix:

Unrevert the patches, taking care about whether they need updating in
consequence of other changes to the Ada front end.  Check carefully
for any other reverted patches, and unrevert them.
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2002-05-04 16:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-04  9:26 Joseph Myers [this message]
2002-09-15 13:09 jsm28

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=E1742EI-0005c9-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).