lkml.org 
[lkml]   [2003]   [Feb]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Bugs sitting in RESOLVED state
Martin J. Bligh wrote:
> 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.

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?

Jeff



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:33    [W:0.031 / U:0.832 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site