This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: GDB `cannotfix' pr state, require PR with xfail `moving forward'.

From: Andrew Cagney <ac131313 at redhat dot com>
To: Daniel Jacobowitz <drow at mvista dot com>
Cc: gdb at sources dot redhat dot com
Date: Fri, 17 Jan 2003 14:47:35 -0500
Subject: Re: GDB `cannotfix' pr state, require PR with xfail `moving forward'.
References: <3E270973.9020702@redhat.com> <3E2858DC.4030405@redhat.com> <20030117192952.GA17549@nevyn.them.org>

GDB has a new category `external'. External bugs can either be `suspended' (I guess that implies that the bug is waiting on the external code to be fixed), or `closed' the external problem has been fixed.

`GDB shall have', it doesn't :-)

Would an external defect relating to GCC 2.95.3, fixed in 3.2, be
marked "closed"?  This would be the one legitimate case for a failure
to refer to a closed bug report?  That seems reasonable at first blush.

That's my guess.

Andrew

References:
- GDB `cannotfix' pr state, require PR with xfail `moving forward'.
  - From: Andrew Cagney
- Re: GDB `cannotfix' pr state, require PR with xfail `moving forward'.
  - From: Andrew Cagney
- Re: GDB `cannotfix' pr state, require PR with xfail `moving forward'.
  - From: Daniel Jacobowitz

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]