From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Stacy Woods <spwoods@us.ibm.com>
Subject: Re: Bugs sitting in RESOLVED state
Date: Thu, 20 Feb 2003 17:36:34 -0800 [thread overview]
Message-ID: <276780000.1045791394@flay> (raw)
In-Reply-To: <3E557F9F.9000803@pobox.com>
>> These bugs have been sitting in RESOLVED state for > 1 week, ie
>> they have fixes, but aren't back in the mainline tree (when they
>> should move to CLOSED state). If the fixes are back in mainline
>> already, could the owner close them out? Otherwise, perhaps we
>> can get those fixes back in?
>
>
> Several of my bugs are sitting in the resolve state because of Bugzilla
> user interface issues. The interface does not allow me to take a bug
> directly from "assigned" to "closed" state. Closed is not even presented
> as an option. If the bug is indeed in the resolved state, then I can
> close the bug. But this two-step process is a bit silly.
OK, I'll ask Jon if we can fix that ...
> Also, several of my 'resolved' bugs have comments that clearly indicate
> the fix has been merged. So, now I must go in a clicking spree, taking
> valuable time away from hacking :) Don't we have kind and gracious
> Bugzilla janitors for this sort of thing?
heh ;-) will try to sort something out for that ... we ought to go through
each one and do a simple check like that, before we send out such lists.
M.
next prev parent reply other threads:[~2003-02-21 1:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-21 1:01 Martin J. Bligh
2003-02-21 1:23 ` Jeff Garzik
2003-02-21 1:36 ` Martin J. Bligh [this message]
2003-02-20 21:14 ` Thomas Molina
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=276780000.1045791394@flay \
--to=mbligh@aracnet.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=spwoods@us.ibm.com \
/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
all inboxes | Powered by JetHome®