On Friday 01 January 2010 06:42:18 Corbin Simpson wrote: > Couple things. > > First, if we're going to start autogenerating headers, can we do GL > API first?
As long as we first fix the Exchange integration in KMail (i.e. it's a bit unfair to bring up mysterious unrelated features as a problem with a patchset.) > (While we're at it, since we're doomed to bring it up every couple > months, can we do automake? Please?) Well, "we" think that the shed should be blue. Of course if red would prove to be better than our current rainbow of colors then surely the shed master would let the others do the painting for him. > For coding conventions, sorry for 4-space tabs in r300 and radeon. I > don't intend to change it though. If coding conventions are SERIOUS > BUSINESS, then can we just write down indent rules? We had those for ages: docs/devinfo.html . > Finally, there are almost certainly already out-of-tree drivers and > state trackers based on 0.1 and 0.2 "versions" of the API. Why wasn't > it a priority to version the API before? Because initially Gallium wasn't supposed to be exposing a stable api and state trackers/drivers were supposed to statically link to the same version. The need and desire for a stable api increased lately to a point where we started thinking about it or at least agreeing that it would be nice thing. z ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
