How would you ideally see this working?Mostly I want to know how to make sure changes "stick" once they are made and deemed or shown to work. If the Linux fixes get back into the DRM CVS, then the only other bit is knowing when the DRM CVS has changed. That sounds like a procmail filter on the commit notify list for DRI if there is one set up.
dri-patches on sourceforge.net.
I've been looking at what's in 2.4 and it's quite divergent from what we've got on the trunk. It is pretty closely related to the xfree 4.2 code, though, and most of the changes seem to be in the 2.4 code.Right now for 2.4 I'm juggling too many conflicting balls, if its all in the DRM CVS then merging stuff added to DRM cvs is a real nobrainer, and since I can do it item by item as it changes its also easy to know when something bad happens.
Are you proposing pulling the dri trunk code into 2.4?
Keith
-------------------------------------------------------
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
