From: R Hill <dirtyepic.sk@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Closing bugs [was: New Bugzilla HOWTO]
Date: Sun, 10 Jul 2005 01:39:18 -0600 [thread overview]
Message-ID: <daqjb7$8m2$1@sea.gmane.org> (raw)
In-Reply-To: <42D027E1.3040602@gmx.net>
Marco Matthies wrote:
> Nathan L. Adams wrote:
> The person reporting the bug can reopen the bug, as he/she is in a
> perfect position to test the fix.
Just a thought I've had from time to time - why can't people other than
the reporter reopen a resolved bug report? I'm thinking that there are
cases where the reporter files a PR that gets marked resolved for
whatever reason and then buggers off. Later someone else comes across
the bug and can either comment in the closed bug and hope someone
notices or file a new report which will inevitably be marked Dupe.
What's the correct thing to do in this situation?
--de.
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-07-10 7:42 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-09 3:52 [gentoo-dev] Re: Closing bugs [was: New Bugzilla HOWTO] Jory A. Pratt
2005-07-09 15:11 ` Nathan L. Adams
2005-07-09 15:16 ` Ciaran McCreesh
2005-07-09 16:04 ` Nathan L. Adams
2005-07-09 16:08 ` Nathan L. Adams
2005-07-09 19:39 ` Marco Matthies
2005-07-09 19:56 ` Nathan L. Adams
2005-07-09 19:59 ` Ciaran McCreesh
2005-07-09 20:39 ` Marco Matthies
2005-07-10 7:39 ` R Hill [this message]
2005-07-10 12:13 ` Duncan
2005-07-10 7:30 ` R Hill
2005-07-10 13:49 ` Nathan L. Adams
2005-07-10 14:18 ` Jon Portnoy
2005-07-10 15:08 ` Nathan L. Adams
2005-07-10 15:19 ` Ciaran McCreesh
2005-07-10 15:32 ` Nathan L. Adams
2005-07-10 15:34 ` Ciaran McCreesh
2005-07-10 22:18 ` Nathan L. Adams
2005-07-10 15:39 ` Diego 'Flameeyes' Pettenò
2005-07-10 19:37 ` Maurice van der Pot
2005-07-10 22:30 ` Nathan L. Adams
2005-07-10 19:27 ` R Hill
2005-07-10 22:20 ` Nathan L. Adams
-- strict thread matches above, loose matches on Subject: below --
2005-07-08 2:08 [gentoo-dev] New Bugzilla HOWTO Chris White
2005-07-07 18:49 ` Simon Stelling
2005-07-07 20:15 ` [gentoo-dev] " Duncan
2005-07-08 11:42 ` [gentoo-dev] Closing bugs [was: New Bugzilla HOWTO] Nathan L. Adams
2005-07-09 1:37 ` [gentoo-dev] " Duncan
2005-07-09 1:50 ` Mike Frysinger
2005-07-09 3:46 ` Nathan L. Adams
2005-07-09 10:11 ` Martin Schlemmer
2005-07-09 14:54 ` Nathan L. Adams
2005-07-09 15:11 ` Jon Portnoy
2005-07-09 16:00 ` Nathan L. Adams
2005-07-09 16:02 ` Stephen P. Becker
2005-07-09 16:20 ` Nathan L. Adams
2005-07-10 0:00 ` Jon Portnoy
2005-07-10 1:06 ` Nathan L. Adams
2005-07-10 2:19 ` Jory A. Pratt
2005-07-10 3:23 ` Nathan L. Adams
2005-07-10 8:59 ` Daniel Drake
2005-07-09 15:44 ` Gregorio Guidi
2005-07-09 16:04 ` Nathan L. Adams
2005-07-09 22:53 ` R Hill
2005-07-10 13:55 ` Nathan L. Adams
2005-07-10 14:33 ` Daniel Drake
2005-07-10 15:14 ` Nathan L. Adams
2005-07-10 15:33 ` Daniel Drake
2005-07-10 14:44 ` Jason Stubbs
2005-07-10 10:18 ` Henrik Brix Andersen
2005-07-10 13:14 ` Nathan L. Adams
2005-07-10 16:23 ` Henrik Brix Andersen
2005-07-09 17:00 ` Mike Frysinger
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='daqjb7$8m2$1@sea.gmane.org' \
--to=dirtyepic.sk@gmail.com \
--cc=gentoo-dev@lists.gentoo.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