Oh! so I totally misunderstood that command...reading the documentation seemed to me git pull already encompass a git fetch and a git merge. also I tried the git pull after the make command and that confirmed the local branch was up-to-date. ok, i will try again after the fetch. thank you.
Mir doesn’t (yet) have a clean API for adding Wayland protocol extensions in a server and, in any case, those that are needed by Ubuntu Touch are simply exposing existing Mir functionality. So, once the necessary protocol extensions are identified, the Mir code is the place to implement them.
Well, given that there is still some battery charging stuff running, even when the main OS is turned off, maybe there is an firmware issue of some sort? Could anyone else with a Nexus5 try and see what happens with a turned off device?
Small update on this: it appears my Nexus5 isn't powering down the wifi chip on shut-down. So if I make sure there is no connection before shutting it down the battery doesn't drain nearly as fast when turned off. Is this something that might be a specific UT issue?
At the risk of revealing the I understand less than I purport to understand, I have one more question: I know this calls for speculation, but do you anticipate that the above mentioned problematic Qt based applications will behave reasonably well (as a stopgap) under the XWayland solution that you are currently developing for Mir?
That is a reasonable expectation, although don't expect immediate progress! (We've not started coding yet,) But Qt applications are largely usable already (and Qt 5.9.4 was a significant improvement on 5.9.3).