On Thu, Dec 12, 2002 at 12:53:46PM +0000, Keith Whitwell wrote: > Alan Hourihane wrote: > >On Thu, Dec 12, 2002 at 01:02:30PM +0000, Alan Cox wrote: > > > >>On Wed, 2002-12-11 at 22:11, D. Hageman wrote: > >> > >>>Alan, > >>> > >>>What would you like to see be implemented to help get the job done. In > >>>other words, what do you need from the DRI team? > >> > >>It takes two to tango so its not just what I need its also what do they > >>need. > >> > >>What I would like to see would be: > >> > >>A single definitive source for the DRM code, one where contributions go > >>back from Linux, from *BSD, from core XFree86 as well as from the DRI > >>project. > >> > >>The ability to track changes to that with reasons so that we can keep a > >>stable DRM and also the 'DRM of the day' visible to the kernel people - > >>perhaps the devel kernel tree having an option for "Development DRM > >>(XFree86 4.4) (Y/M/N)". > > > > > >For 'stable DRM' you need to stick with XFree86 4.2.0 and the DRM modules > >that ship with 4.2.0. For 'DRM of the day' use the DRI trunk. > > Or 4.2.x for most recent x? What about bugs that are found in the modules > after XFree is released? Or api changes within the kernel?
Sorry - yes 4.2.1 or most recent 4.2.x. As for bugs found or api changes they should be submitted back to XFree86 so they can be applied to the stable xf-4_2-branch ready for a new 4.2.x release - if there was to be one. Alan. ------------------------------------------------------- This sf.net email is sponsored by: With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel http://hpc.devchannel.org/ _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
