| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
On 10/31/2012 08:52 AM, Tomáš Chvátal wrote: |
| 5 |
> 2012/10/31 Dirkjan Ochtman <djc@g.o>: |
| 6 |
>> That's rather unsurprising... |
| 7 |
>> |
| 8 |
>> If you're going to file bugs "in a semi-automated manner", might |
| 9 |
>> as well try to assign to the correct maintainer? |
| 10 |
>> |
| 11 |
> Yep he should've assign them, but anyway the annoying elog |
| 12 |
> messages are an issue. And quite few packages suffer from it :-) |
| 13 |
> |
| 14 |
> Tom |
| 15 |
> |
| 16 |
I disagree on most of them (and have marked the KDE-related bugs as |
| 17 |
WONTFIX appropriately). Messages that tell the user about config |
| 18 |
options, or "for x functionality install y" (at least until we get |
| 19 |
SDEPEND or something similar added to portage) should show up every |
| 20 |
time in my opinion. Only initial config and "you just enabled (flag)" |
| 21 |
really merits this. Basically, I would rather the user get too many |
| 22 |
elog messages than not enough, since I feel that a lot of people skip |
| 23 |
over them anyway and so the "only display once" method makes it far |
| 24 |
too easy for important messages to get lost in the shuffle. |
| 25 |
Chris Reffett |
| 26 |
-----BEGIN PGP SIGNATURE----- |
| 27 |
Version: GnuPG v2.0.19 (GNU/Linux) |
| 28 |
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ |
| 29 |
|
| 30 |
iEYEARECAAYFAlCRQQAACgkQ23laikJhg1Q+aQCeLfXsAmbtXNGOcBzM/vJaMat2 |
| 31 |
ly0AoKFzB3tPLaSO2RK0p2rWd6CoKMXm |
| 32 |
=J+3S |
| 33 |
-----END PGP SIGNATURE----- |
Archives