On Wed, Nov 17, 2010 at 08:58:43PM -0800, Evan Broder wrote:
>Based on some off-list discussion, I'd like to try a different
> angle for the Lua patches I submitted a week or two ago. For context,
> Ubuntu is interested in setting gfxpayload=keep as often as we can in
> the next release [1]. Si
On Thu, Nov 18, 2010 at 7:52 PM, Brendan Trotter wrote:
> Hi,
>
> On Thu, Nov 18, 2010 at 3:28 PM, Evan Broder wrote:
>> Based on some off-list discussion, I'd like to try a different
>> angle for the Lua patches I submitted a week or two ago. For context,
>> Ubuntu is interested in setting gfx
Hi,
On Thu, Nov 18, 2010 at 3:28 PM, Evan Broder wrote:
> Based on some off-list discussion, I'd like to try a different
> angle for the Lua patches I submitted a week or two ago. For context,
> Ubuntu is interested in setting gfxpayload=keep as often as we can in
> the next release [1]. Since
On Thu, Nov 18, 2010 at 12:32:20PM +0100, Vladimir 'φ-coder/phcoder' Serbinenko
wrote:
> On 11/18/2010 05:58 AM, Evan Broder wrote:
> > As a strawman, I propose adding the "hwmatch" command:
> >
> > Usage: hwmatch MATCHLIST [BASECLASS]
> >
> > MATCHLIST is a file containing a list of hardware id
On 11/18/2010 05:58 AM, Evan Broder wrote:
> Hi -
>Based on some off-list discussion, I'd like to try a different
> angle for the Lua patches I submitted a week or two ago. For context,
> Ubuntu is interested in setting gfxpayload=keep as often as we can in
> the next release [1]. Since gfxpayl
Hi -
Based on some off-list discussion, I'd like to try a different
angle for the Lua patches I submitted a week or two ago. For context,
Ubuntu is interested in setting gfxpayload=keep as often as we can in
the next release [1]. Since gfxpayload=keep doesn't work with all
hardware/driver combin
