| 1 |
I've noticed that too. In fact, I had several ebuilds I submitted that |
| 2 |
were marked as such and I emerged today and noticed my ebuilds had been |
| 3 |
added to the tree. Unfortunately, since mine where marked RESOLVED |
| 4 |
LATER, the new ebuilds were in fact submitted by someone else so I |
| 5 |
didn't get credit. grrrr. |
| 6 |
|
| 7 |
Tom Prado |
| 8 |
|
| 9 |
Yannick Koehler wrote: |
| 10 |
> -----BEGIN PGP SIGNED MESSAGE----- |
| 11 |
> Hash: SHA1 |
| 12 |
> |
| 13 |
> There's several bug that are mark RESOLVED LATER. When such bugs get marked |
| 14 |
> as such they don't get into the default search parameter and therefore result |
| 15 |
> in multiple duplicate as people try to search for the package that are |
| 16 |
> missing and then don't find it and file a bug. |
| 17 |
> |
| 18 |
> It would be nice that the RESOLVED LATER be mark as default inside the query |
| 19 |
> with the amount of bug there is on that state. |
| 20 |
> |
| 21 |
> Or, why not leave the bug as NEW/ASSIGN/REOPEN but mark the target as being |
| 22 |
> post-1.4? |
| 23 |
> |
| 24 |
> - -- |
| 25 |
> |
| 26 |
> Yannick Koehler |
| 27 |
> -----BEGIN PGP SIGNATURE----- |
| 28 |
> Version: GnuPG v1.0.6 (GNU/Linux) |
| 29 |
> Comment: For info see http://www.gnupg.org |
| 30 |
> |
| 31 |
> iD8DBQE9rVK8fuKOJNEyL1URAgi7AJ0Xotn+hqDIlg0oN0h4e2aoRD+JPwCdHLm7 |
| 32 |
> B3lkrZHzx0QLCCEpTXHGcFo= |
| 33 |
> =kWU9 |
| 34 |
> -----END PGP SIGNATURE----- |
| 35 |
> |
| 36 |
> _______________________________________________ |
| 37 |
> gentoo-dev mailing list |
| 38 |
> gentoo-dev@g.o |
| 39 |
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev |
Archives