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: other/2774: Missing PRs
Date: Tue, 08 May 2001 10:06:00 -0000	[thread overview]
Message-ID: <E14xAvV-0007FN-00@jsm28.trin.cam.ac.uk> (raw)

>Number:         2774
>Category:       other
>Synopsis:       Missing PRs
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue May 08 10:06:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Joseph S. Myers
>Release:        3.0 20010506 (prerelease)
>Organization:
none
>Environment:
System: Linux digraph 2.2.19 #1 Wed Mar 28 16:01:38 UTC 2001 i686 unknown
Architecture: i686

	
host: i686-pc-linux-gnu
build: i686-pc-linux-gnu
target: i686-pc-linux-gnu
configured with: ../gcc-3cvs/configure --prefix=/opt/gcc/snapshot --disable-shared --enable-threads=posix --with-system-zlib --disable-libgcj
>Description:

Some PRs are missing from the GNATS database and need to be restored
from list archives.  Others appear in two places in the GNATS
database.

>How-To-Repeat:

See http://gcc.gnu.org/ml/gcc/2001-05/msg00221.html

PRs in two places in the database: 2138 2144 2234 2354

Assuming that each PR should be in exactly one category directory:

2138: the category "c++" copy should go, the "libstdc++" one should stay.
2144: the category "pending" copy should go, the "c++" one should stay.
2234: the category "preprocessor" copy should go, the "c++" one should
stay.
2354: the category "c++" copy should go, the "target" one should stay.

PRs missing: 2386 2389 2392 2394 2397 2403 2404 2419 2420 2426

>Fix:

(This PR should be assigned to overseers.)
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2001-05-08 10:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-08 10:06 Joseph Myers [this message]
2001-06-12 12:55 jsm28
2001-10-04 18:04 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=E14xAvV-0007FN-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).