This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: When may I close a 5.1.1 PR?
- From: Andrew Cagney <ac131313 at cygnus dot com>
- To: Michael Elizabeth Chastain <mec at shout dot net>
- Cc: gdb at sources dot redhat dot com
- Date: Mon, 11 Feb 2002 12:24:09 -0500
- Subject: Re: When may I close a 5.1.1 PR?
- References: <200202110204.g1B24xf08198@duracef.shout.net>
> So last week I filed this PR:
>
> http://sources.redhat.com/cgi-bin/gnatsweb.pl?database=gdb&cmd=view&pr=334
>
> This is a test failure in 5.1.1, but it is fixed in gdb HEAD (the mainline).
>
> As a general question, when is a good time to close a PR that is fixed
> in the mainline but not in the 5.1 branches:
>
> . after gdb 5.2 is released?
> . after gdb 5.2 is branched?
> . as soon as the bug is fixed in mainline?
>
> I'll be happy to do whatever the voices in my mailbox tell me. :)
I'm just happy to see the problem and fix recorded. Probably close it
since I assume no one has any intention of fixing it on the branch.
--
As an aside, I've been wondering what to do with the page:
http://sources.redhat.com/gdb/bugs/
I was thinking that it should just jump to the bug database. However,
looking around I've noticed that other projects have (for an equivalent
page) used it to ``educate'' the reader as to how to submit a better bug
report and where to find potential fixes.. I'm not sure we want to go
down that path. However, having the gdb/bugs/ page draw peoples
attention to the current sources (http://sources.redhat.com/gdb/current)
could help.
thoughts?
Andrew