| 1 |
I've looked at the actual DB behind bugzilla, and that seems to be the |
| 2 |
only bug having that such situation, with a resolved-like status, but no |
| 3 |
resolution, all the other bugs look fine. *shrug* |
| 4 |
|
| 5 |
-Jeffrey |
| 6 |
|
| 7 |
On Tue, 2005-05-17 at 17:05 +0300, Alin Dobre wrote: |
| 8 |
> -----BEGIN PGP SIGNED MESSAGE----- |
| 9 |
> Hash: SHA1 |
| 10 |
> |
| 11 |
> |
| 12 |
> Jonathan Smith wrote: |
| 13 |
> > Georgi Georgiev wrote: |
| 14 |
> > |
| 15 |
> >>>maillog: 17/05/2005-16:04:20(+0300): Alin Dobre types |
| 16 |
> >>> |
| 17 |
> >>>>>*** This bug has been marked as a duplicate of 12745 *** |
| 18 |
> >>>> |
| 19 |
> >>>>Here it is, the last row. |
| 20 |
> >>> |
| 21 |
> >>> |
| 22 |
> >>>But in the headers it says: |
| 23 |
> >>> |
| 24 |
> >>>Status: RESOLVED |
| 25 |
> >>>Resolution: |
| 26 |
> >>> |
| 27 |
> > |
| 28 |
> > |
| 29 |
> > right. what i was saying was that it is very nice to see the reason for |
| 30 |
> > resolution in the summary section. |
| 31 |
> |
| 32 |
> something like this: |
| 33 |
> |
| 34 |
> What |Removed |Added |
| 35 |
> - |
| 36 |
> ---------------------------------------------------------------------------- |
| 37 |
> Status|NEW |RESOLVED |
| 38 |
> Resolution| |DUPLICATE |
| 39 |
> |
| 40 |
> yes, indeed, the Resolution is empty, now. |
| 41 |
|
| 42 |
> -----END PGP SIGNATURE----- |
| 43 |
|
| 44 |
-- |
| 45 |
gentoo-dev@g.o mailing list |
Archives