public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joe Buck <jbuck@synopsys.com>
To: jsm28@cam.ac.uk (Joseph S. Myers)
Cc: Joe.Buck@synopsys.COM (Joe Buck), gcc@gcc.gnu.org
Subject: Re: status of high-priority GNATS bugs
Date: Tue, 22 Oct 2002 21:24:00 -0000	[thread overview]
Message-ID: <200210222250.g9MMopF14941@piper.synopsys.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0210222340430.5599-100000@kern.srcf.societies.cam.ac.uk> from "Joseph S. Myers" at Oct 22, 2002 11:44:38 PM

> On Tue, 22 Oct 2002, Joe Buck wrote:
> 
> > Misc: unclear whether this is priority "high"
> > 6558 (wrongly reverted Ada patches?)
> 
> The patches, including bug fixes, were applied before 3.1 branched and 
> wrongly reverted after then.  ada/6919 is a similar problem (patches only 
> ever applied to the branch, not mainline), also "high".

Thanks, then it should go into the category 

"Reported against the trunk, confirmed not present in 3.2 branch"

Right now I'm mainly interested in the releasability of 3.2.1.  Still
doesn't look good.


  reply	other threads:[~2002-10-22 22:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-22 15:51 Joe Buck
2002-10-22 17:50 ` Janis Johnson
2002-10-22 18:08   ` Zack Weinberg
2002-10-22 19:23   ` Joe Buck
2002-10-22 20:12 ` Joseph S. Myers
2002-10-22 21:24   ` Joe Buck [this message]
2002-10-22 21:13 ` David S. Miller
2002-10-23  2:59   ` Mark Mitchell
2002-10-22 23:24 ` Kaveh R. Ghazi
2002-10-22 23:26 ` Kaveh R. Ghazi
  -- strict thread matches above, loose matches on Subject: below --
2002-10-22 22:28 Matthias Klose
2002-10-22 18:11 Brad Lucier
2002-10-22 18:33 ` Joe Buck
2002-10-22 18:52 ` Joe Buck
2002-10-23  4:49 ` Christian Jönsson
2002-05-03 16:27 Joe Buck
2002-05-04  8:07 ` Richard Earnshaw

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=200210222250.g9MMopF14941@piper.synopsys.com \
    --to=jbuck@synopsys.com \
    --cc=Joe.Buck@synopsys.COM \
    --cc=gcc@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).