| 1 |
>>>>> On Thu, 12 Dec 2019, Mike Gilbert wrote: |
| 2 |
|
| 3 |
> On Wed, Nov 27, 2019 at 11:14 PM Michał Górny <mgorny@g.o> wrote: |
| 4 |
>> On Wed, 2019-11-27 at 23:49 +0100, Ulrich Mueller wrote: |
| 5 |
|
| 6 |
>> > The difference is that there is now a QA warning for something that |
| 7 |
>> > is perfectly within the spec. Maybe the extra verboseness would be |
| 8 |
>> > enough, but the eqawarn line should be omitted? It doesn't provide |
| 9 |
>> > any info that isn't already present in the output of patch itself. |
| 10 |
>> |
| 11 |
>> It helps people understand why some patches throw a wall of text |
| 12 |
>> while others don't. |
| 13 |
|
| 14 |
> It also triggers pointless bug reports. Please remove this. |
| 15 |
|
| 16 |
I don't like that eqawarn either (see above). |
| 17 |
|
| 18 |
OTOH, users shouldn't normally have "qa" in PORTAGE_ELOG_CLASSES, |
| 19 |
so they won't see the warning? |
| 20 |
|
| 21 |
Ulrich |
Archives