already have BC for the API/ABI
any progress on this ancient bug?
It seems that this crew were simply never planning to resolve this bug at all, so I'm going to reassign it to xorg-bugzilla-noise.
No, it's not true that "this crew" were "never planning to resolve it." After you, i.e. you being Daniel Stone, deleted my sudo on fd.o, then disabled ssh, later removed my account completely, and didn't restore any of it when complaints were raised, I just gave up on the entire lot of you. Supremely unprofessional in my estimation and just generally bad form. Shame on you.
I wasn't aware of 'disabling ssh', and 'removing [your] account altogether', but thanks for the clarification.
Does anyone remember the details of what the incompatibilities actually are? Where can the 2.0 code/docs be found at now?
Assigning to myself.
FWIW, interesting history on this bug (details of incompatibilities) can be found on the xorg@ and xorg_arch@ archives going back to around this time last year. If xwsodf archives would be useful, let me know.
as being the oldest open Xorg bug, i would be rather pleased if this could see resolution in 6.9.
I think I'm going to close this one as "WONTFIX". The problems with the proposed Xinerama standard run far deeper than a simple bugfix, and it needs to be reworked, not just hacked into being less broken. (For starters, there is no Xinerama 2.0 - the proposed standard defines its protocol as 1.2, despite being incompatible with the existing 1.0 & 1.1 implementations, so we can't implement the standard as written, and integrating something else would miss the point of the original standardization exercise.) Since the new protocol isn't even in HEAD at this point, only buried deep in removed past revs to our CVS and a source tree on sourceforge.net that no one has touched in years, this isn't a 6.9/7.0 blocker, and would be introducing a new untested feature after our feature freeze, so I'm removing the "blocks 1690" as well. When the standard process started, Xinerama was so new that there was no existing code to worry about being compatible with. 7 years later, that's no longer the case, and the proposed standard needs to have a major overhaul to make it useful and usable. This needs to go back to the X.Org Architecture Working Group.
WONTFIX counts as a resolution ;)
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.