Linked by Thom Holwerda on Mon 9th Sep 2013 21:22 UTC, submitted by lucas_maximus
X11, Window Managers Intel on Ubuntu's XMir:

We do not condone or support Canonical in the course of action they have chosen, and will not carry XMir patches upstream.

Ubuntu has to do virtually all its work on Xmir drivers by itself. No one else supports it.

Thread beginning with comment 571651
To read all comments associated with this story, please click here.
Comment by aaronb
by aaronb on Mon 9th Sep 2013 21:28 UTC
aaronb
Member since:
2005-07-06

Is there any technical reason for why these patches were not accepted?

Reply Score: 4

RE: Comment by aaronb
by silviucc on Mon 9th Sep 2013 22:09 in reply to "Comment by aaronb"
silviucc Member since:
2009-12-05

Well, technically Intel is invested heavily in Wayland. Hah, nice use of the word "technically" ;)

Anyway, this only means that Canonical has a bit more work on their hands. It's basically people telling them something along the lines of "You want Mir instead of Wayland then make it work yourselves".

Reply Parent Score: 6

RE[2]: Comment by aaronb
by Hiev on Mon 9th Sep 2013 22:13 in reply to "RE: Comment by aaronb"
Hiev Member since:
2005-09-27

We do not condone or support Canonical in the course of action they have chosen

That is to vague, what are they *exactly* not condoning?

Reply Parent Score: 4

RE[2]: Comment by aaronb
by darknexus on Tue 10th Sep 2013 00:09 in reply to "RE: Comment by aaronb"
darknexus Member since:
2008-07-15

Anyway, this only means that Canonical has a bit more work on their hands. It's basically people telling them something along the lines of "You want Mir instead of Wayland then make it work yourselves".

Yep, and Canonical will do just that, resulting in graphics libraries needing to support two new backends instead of one, and neither will be done well. Fucking wonderful!

Reply Parent Score: 4

RE: Comment by aaronb
by Delgarde on Tue 10th Sep 2013 01:06 in reply to "Comment by aaronb"
Delgarde Member since:
2008-08-19

Is there any technical reason for why these patches were not accepted?


The same one as used by the KWin developers - an unwillingness to accept patches that are useful only for a single distribution. Such patches are only a maintenance burden for upstream developers, adding extra code paths that they don't use, but which need to be kept working when making changes.

And it's not enough to say "Canonical devs will maintain it", because even ignoring trust issues, reality doesn't work that way - there are no clear demarcations between "stuff for upstream devs" and "stuff for Mir devs". It's *all* stuff for upstream devs...

Reply Parent Score: 5