Re: [Mesa-dev] [V3 PATCH 0/8] mesa: Naming MESA_FORMATs to a specification

2014-01-17 Thread Mark Mueller
On Fri, Jan 17, 2014 at 2:43 AM, Erik Faye-Lund wrote: > On Fri, Jan 17, 2014 at 9:22 AM, Christian König > wrote: > > But as a general note on writing patches: Please limit the subject line > to a > > sane length! Something between 60 and 80 chars should be ok. > > Indeed. The regex patterns ar

Re: [Mesa-dev] [V3 PATCH 0/8] mesa: Naming MESA_FORMATs to a specification

2014-01-17 Thread Erik Faye-Lund
On Fri, Jan 17, 2014 at 9:22 AM, Christian König wrote: > But as a general note on writing patches: Please limit the subject line to a > sane length! Something between 60 and 80 chars should be ok. Indeed. The regex patterns are nice to have. But please, put them in the *body* of the commit messa

Re: [Mesa-dev] [V3 PATCH 0/8] mesa: Naming MESA_FORMATs to a specification

2014-01-17 Thread Christian König
I haven't followed the discussion so I can't judge weather or not this is a good idea. But as a general note on writing patches: Please limit the subject line to a sane length! Something between 60 and 80 chars should be ok. Thanks, Christian. Am 17.01.2014 07:37, schrieb Mark Mueller: This

[Mesa-dev] [V3 PATCH 0/8] mesa: Naming MESA_FORMATs to a specification

2014-01-16 Thread Mark Mueller
This series introduces a specification for 3 types of MESA_FORMAT names - Type A (array formats), Type C (compressed formats), and Type P (packed formats), and then performs a series of substitutions grouped by type. Builds of all default gallium and DRI drivers were verified and no regressions wer