On Tue, Sep 4, 2012 at 7:40 PM, Eric Anholt wrote:
> Brian Paul writes:
>
>> On 09/02/2012 01:42 PM, Fabio Pedretti wrote:
>>> I noticed that mesa bug report got CCed to mesa-dev list, while driver mesa
>>> bug
>>> went to dri-devel.
>>
>> That does seem kind of weird.
>>
>>> Is this intended, w
Brian Paul writes:
> On 09/04/2012 11:40 AM, Eric Anholt wrote:
>> Brian Paul writes:
>>
>>> On 09/02/2012 01:42 PM, Fabio Pedretti wrote:
I noticed that mesa bug report got CCed to mesa-dev list, while driver
mesa bug
went to dri-devel.
>>>
>>> That does seem kind of weird.
>>>
On 09/04/2012 11:40 AM, Eric Anholt wrote:
Brian Paul writes:
On 09/02/2012 01:42 PM, Fabio Pedretti wrote:
I noticed that mesa bug report got CCed to mesa-dev list, while driver mesa bug
went to dri-devel.
That does seem kind of weird.
Is this intended, why don't use mesa-dev for all mes
Brian Paul writes:
> On 09/02/2012 01:42 PM, Fabio Pedretti wrote:
>> I noticed that mesa bug report got CCed to mesa-dev list, while driver mesa
>> bug
>> went to dri-devel.
>
> That does seem kind of weird.
>
>> Is this intended, why don't use mesa-dev for all mesa
>> related bug instead and u
On 09/02/2012 01:42 PM, Fabio Pedretti wrote:
I noticed that mesa bug report got CCed to mesa-dev list, while driver mesa bug
went to dri-devel.
That does seem kind of weird.
Is this intended, why don't use mesa-dev for all mesa
related bug instead and use dri-devel for libdrm/kernel modules
I noticed that mesa bug report got CCed to mesa-dev list, while driver mesa bug
went to dri-devel. Is this intended, why don't use mesa-dev for all mesa
related bug instead and use dri-devel for libdrm/kernel modules only?
___
mesa-dev mailing list
mesa
