On Tue, Mar 26, 2013 at 8:35 PM, Vishal Bhoj vishal.bhoj@linaro.org wrote:
On 27 March 2013 01:01, Alexander Sack asac@linaro.org wrote:
On Sat, Mar 23, 2013 at 1:08 PM, Bernhard Rosenkränzer bernhard.rosenkranzer@linaro.org wrote:
Hi,
On 23 March 2013 05:36, Vishal Bhoj vishal.bhoj@linaro.org wrote:
Bero, Do we need these 2 manifest: default.xml linaro-default.xml
default.xml is the AOSP manifest, linaro-default.xml is the AOSP manifest + some changes to pull in Linaro trees. I think linaro-default.xml can be obsoleted because tracking.xml essentially replaces it, there's no build that uses it.
I kind of prefer the use of linaro-default.xml rather than tracking.xml for our unified manifest... Can we use that name?
If you look at the next comment below,the tracking.xml is going to become the default.xml in our case.
That sounds much better. Thanks for pointing helping me read!
As for default.xml, we may want to just rename tracking.xml to default.xml -- that's essentially what it is (our version of the file found upstream). That would also allow us to "git merge android-4.3_r1" even in platforms/manifest, and it would allow repo to do the right thing without a -m flag.
ttyl bero
linaro-android mailing list linaro-android@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-android
-- Alexander Sack Director, Linaro Platform Engineering http://www.linaro.org | Open source software for ARM SoCs http://twitter.com/#%21/linaroorg - http://www.linaro.org/linaro-blog