On Fri, Apr 16, 2004 at 05:41:39PM -0400, David Dawes wrote: >On Wed, Apr 14, 2004 at 05:33:48PM -0400, Tristan Van Berkom wrote: >>Hi team, >> I'm not so sure about the proper patching etiquette so I'll ask here, >>I seem to have rights to do whatever I want with a bug, so I filed the bug, >>I fixed the bug (not in bugzilla), attatched a "proposed patch", assigned >>the bug to myself; but I dont think I should be able to mark it fixed >>if its not in cvs HEAD, correct ? > >As far as I know there are no restrictions on who can do what, except >for configuration-type things that only the bugzilla admin can do. > >>Here is the bug info: >> http://bugs.xfree86.org/show_bug.cgi?id=1332 >> >>One more thing, Is it desireable that this version of driver be >>compileable for X 3.3.x series ? > >XFree86 3.3.x is no longer maintained. The general preference is to >not include compatiblity code in drivers. I don't know if the author >of the input drivers with 3.3.x compatility code still has a need to >keep it around.
In the absence of anyone saying that they still need the pre-4.0 compatibility in the input drivers, I removed all that stuff a few days ago. Some of it was for our unreleased pre-4.0 module support before the ugly "MAGIC" hacks were replaced with something better, and that was definitely of no use to anyone. For those who test the experimental snapshots instead of the current CVS code, these changes are included in yesterday's 4.4.99.4 snapshot. It'd be a good idea to test the input drivers to make sure nothing got broken. I also ported Miroslav Halas' mulit-head elographics driver fix to some of the other input drivers that look like they needed it. A few others probably need it too. Anyone who has multi-head configurations that use these input devices should test that it all works. David _______________________________________________ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
