Hi,
As part of the unification of manifest, we have been merging all the manifests into single tracking.xml manifest. There are few manifest which are deprecated and need to be removed. The mail is sent to all the people who have a stake in the builds which were using these manifest. Please reply to this mail if any of these manifest are still needed by any of the projects:
staging-origen.xml: Origen Build (Now deprecated) staging-vexpress-rtsm.xml: RTSM Build (Now supported in vexpress builds) tracking-panda.xml: Tracking the Landing team kernel. Will be removed since no work is going on. tracking-vexpress-rtsm-mp.xml: RTSM Build (Now supported in vexpress builds) staging-vexpress-rtsm-isw.xml: RTSM IKS build which is no more supported. staging-vexpress.xml: Vexpress Manifest to track staging kernel. tracking-snowball.xml: Tracking the landing team kernel. Will be removed since no work is going on.
Bero, Do we need these 2 manifest: default.xml linaro-default.xml
Most of the engineering builds are now supported from tracking.xml manifest with the help of groups. Moving forward any new project will be integrated into this manifest.
Regards, Vishal
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.
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
On 23 March 2013 17:38, 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.
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.
That was the next logical step to do. Lets do it at the beginning of next cycle.
ttyl bero
agree
On 23 March 2013 14:45, Vishal Bhoj vishal.bhoj@linaro.org wrote:
On 23 March 2013 17:38, 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.
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.
That was the next logical step to do. Lets do it at the beginning of next cycle.
ttyl bero
Here are the changes for review:
http://review.android.git.linaro.org/3466 http://review.android.git.linaro.org/3467 http://review.android.git.linaro.org/3468 http://review.android.git.linaro.org/3469 http://review.android.git.linaro.org/3470 http://review.android.git.linaro.org/3471
I created a few test builds with all these changes to verify. Please review comments on gerrit or reply to this mail. https://android-build.linaro.org/builds/~vishalbhoj/unified-manifest-arndale... https://android-build.linaro.org/builds/~vishalbhoj/unified-manifest-galaxyn... https://android-build.linaro.org/builds/~vishalbhoj/vexpress-unified-manifes...
On 24 March 2013 16:02, Axel Fagerstedt axel.fagerstedt@linaro.org wrote:
agree
On 23 March 2013 14:45, Vishal Bhoj vishal.bhoj@linaro.org wrote:
On 23 March 2013 17:38, 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.
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.
That was the next logical step to do. Lets do it at the beginning of next cycle.
ttyl bero
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?
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
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.
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
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
On 26 March 2013 20:31, Alexander Sack asac@linaro.org wrote:
I kind of prefer the use of linaro-default.xml rather than tracking.xml for our unified manifest... Can we use that name?
We can -- but it probably makes more sense to just use default.xml -- that's what AOSP uses (and therefore, what will get updated by "git merge android-4.3_r1"), and it's what people get when they don't pass a -m argument to repo init.
ttyl bero
I have merged all the patches and updated the builds. Let me know if you see any issues with the builds.
On 26 March 2013 23:17, Vishal Bhoj vishal.bhoj@linaro.org wrote:
Here are the changes for review:
http://review.android.git.linaro.org/3466 http://review.android.git.linaro.org/3467 http://review.android.git.linaro.org/3468 http://review.android.git.linaro.org/3469 http://review.android.git.linaro.org/3470 http://review.android.git.linaro.org/3471
I created a few test builds with all these changes to verify. Please review comments on gerrit or reply to this mail.
https://android-build.linaro.org/builds/~vishalbhoj/unified-manifest-arndale...
https://android-build.linaro.org/builds/~vishalbhoj/unified-manifest-galaxyn...
https://android-build.linaro.org/builds/~vishalbhoj/vexpress-unified-manifes...
On 24 March 2013 16:02, Axel Fagerstedt axel.fagerstedt@linaro.orgwrote:
agree
On 23 March 2013 14:45, Vishal Bhoj vishal.bhoj@linaro.org wrote:
On 23 March 2013 17:38, 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.
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.
That was the next logical step to do. Lets do it at the beginning of next cycle.
ttyl bero
linaro-android@lists.linaro.org
-
Alexander Sack -
Axel Fagerstedt -
Bernhard Rosenkränzer -
Vishal Bhoj