I've looked at the actual DB behind bugzilla, and that seems to be the only bug having that such situation, with a resolved-like status, but no resolution, all the other bugs look fine. *shrug*
-Jeffrey On Tue, 2005-05-17 at 17:05 +0300, Alin Dobre wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > Jonathan Smith wrote: > > Georgi Georgiev wrote: > > > >>>maillog: 17/05/2005-16:04:20(+0300): Alin Dobre types > >>> > >>>>>*** This bug has been marked as a duplicate of 12745 *** > >>>> > >>>>Here it is, the last row. > >>> > >>> > >>>But in the headers it says: > >>> > >>>Status: RESOLVED > >>>Resolution: > >>> > > > > > > right. what i was saying was that it is very nice to see the reason for > > resolution in the summary section. > > something like this: > > What |Removed |Added > - > ---------------------------------------------------------------------------- > Status|NEW |RESOLVED > Resolution| |DUPLICATE > > yes, indeed, the Resolution is empty, now. > -----END PGP SIGNATURE----- -- gentoo-dev@gentoo.org mailing list