From: Andrew Cagney <ac131313@cygnus.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: gdb@sources.redhat.com
Subject: Re: When may I close a 5.1.1 PR?
Date: Mon, 11 Feb 2002 09:24:00 -0000 [thread overview]
Message-ID: <3C67FE39.9000700@cygnus.com> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2002-02-11 17:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-10 18:05 Michael Elizabeth Chastain
2002-02-10 22:43 ` Eli Zaretskii
2002-02-11 9:24 ` Andrew Cagney [this message]
2002-02-11 18:54 Michael Elizabeth Chastain
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=3C67FE39.9000700@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb@sources.redhat.com \
--cc=mec@shout.net \
/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