> Since our CVS situation has changed, the policy has also changed. The docs, > unfortunately, have not. As near as I can tell, the situation is as follows: > > - Client-side driver development happens in the Mesa CVS trunk. Stable code > lives in a branch. > > - DRM driver development happens in the DRI CVS trunk. Stable code lives in > the kernel tree.
I consider the kernel tree stable and also the DRM tree living in the Xorg extras/drm.. when we merge up to the Xorg tree/kernel again I'll stablise... also remember you don't need to do use the new core code yet, just build in linux-2.6 directory.... it shouldn't have moved, that is why the core stuff is separate at the moment... > > Based on that, how does the currently shipping kernel (2.6.8.1 still, right?) > fare? Well via isn't shipped as it still (??) has security problems, or if they are fixed no-one as requested me to pull it up to the kernel yet ... At the moment I'm sorta cherry picking CVS for pushing to Linus, I'm taking the things that look stable and good and pushing them up, I'm going to try and get CVS into a bk tree for the -mm tree so at least it gets some testing.... but again this won't affect via/savage/mach64 as they are all persumed unstable (Alan says I should put them in root only, but I don't like defining interfaces until people are happy here.. I know savage drm was pretty non-existant the last time I looked...) Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
