On 02/10/13 00:10, Daniel van Vugt wrote:
Do we have a roadmap for how to deal with the future of Mir input?
I mean, Mir uses Android input. When there's a bug or missing feature,
do we intend to maintain and branch the Android input code? Is that
more desirable than Mir having its own impleme
Hello Mir Developers,
First off -- I'm sorry to read yesterday's news about Mir+XMir not shipping by
default, but I hope it offers you some breathing space -- it's been exciting and
inspirational watching your pace of development!
Anyway, one question not (explicitly) answered in the FAQ you
Hi Joe -
first thanks for the kind words & willingness to try out Xmir.
As to receiving more updates in 13.10 per se, that is unlikely to happen
since 13.10 is in a freeze state (see
https://wiki.ubuntu.com/SaucySalamander/ReleaseSchedule) and we will be
moving into our development phase for 14.04
Last time i was tinkering with the Nexus 7 (presumably the older
model, not the Nexus 7HD), most things were working, except there was
an undiagnosed problem with hybris and the nexus 7 hwc. The nvidia
drivers use a fair amount of the pthread api that the other drivers
don't use (such as process-sh
Find attached a script you can use to bump the ABI on libmirserver to save
time doing it manually.
Run from the bzr checkout with:
$ chmod +x bump_abi.py
$ ./bump_abi.py
Enjoy!
--Robert
bump-abi.py
Description: Binary data
--
Mir-devel mailing list
Mir-devel@lists.ubuntu.com
Modify settings or
note...with the script, you still have to manually take care of the
0.0.whatever-0ubtunu(1not2) at the top of changelog
and you still have to get MIR_VERSION_PATCH # in CMakeList.txt at the top
dir level
On Wed, Oct 2, 2013 at 7:37 PM, Robert Ancell
wrote:
> Find attached a script you can use to
I think there are likely many case where we fear an ABI break is
happening when really it's not. Like some of last night's landings.
In future I shall have to remind myself to point this out in the MP
description... "I'm changing the server headers but it's not an ABI/API
break".
Of course,
we definitely broke in the last round
On Wed, Oct 2, 2013 at 10:20 PM, Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:
> I think there are likely many case where we fear an ABI break is happening
> when really it's not. Like some of last night's landings.
>
> In future I shall have to re
