Hi -
Alexander was asking how linaro-androidization-tracking is maintained
(hope you are feeling better Alexander).
I made a 90-slide presentation about it at the last Connect, you can
find the slides here
http://people.linaro.org/~andygreen/lttools-introduction.pdf
and the tools here
http://git.linaro.org/gitweb?p=people/andygreen/lt-tools.git;a=summary
In a nutshell common-3.0 from Google is a history tree, so detecting new
patches on there is clear enough. John Stultz saw it had come back
recently and dropped me a note it had been updated. I asked Jassi to
isolate the new patches and send them to me.
I use lt-tools to distribute any new patches between the topics, then
reapply it to my android-ready branch and confirm it builds and works
before pushing.
lt-tools also takes care of the tracking action, it's important
everything is on the same Linus HEAD basis so I routinely rebase
linaro-androidization-tracking along with my other tracking branches, as
of last week it's on 3.2-rc4.
Actually, l-a-t is low maintainence since it's far from every day new
patches are coming on common-3.0, and so far on 3.2 cycle there was no
serious uplevel conflict between the androidization patch load and Linus
HEAD changes.
If we have someone else now who wants to maintain it, I think that's
fine with the provisos we should maintain the topic structure and look
at further refactor there, and we need a new approach to deal with
rebase points that more than one tree can rendezvous at --->
Right now when my tracking branches are in as reasonable a shape on one
Linus HEAD basis as they will get, I randomly pull a new basis from what
happens to be on Linus' tree that moment, and rebase everything on my
side against that (including up until now l-a-t at the same time). That
won't really scale to other LTs and WGs all randomly sampling Linus HEAD
at different random points as their basis.
Scott mentioned that there's a desire to see more KWG content at least
on tracking, I think that's a great idea. One way to solve both those
problems would be to no longer have LTs base off Linus HEAD but from a
new tree which is Linus HEAD + "linux-linaro-tracking", as it were, with
these other topics already merged in. So long as this rebases against
Linus HEAD really often, like daily at least in the early -rcs, carrying
its topic content with it, and matching linaro-androidization-tracking
is available, that would be a good way for all the LT trees to both get
any Linaro-specific content and increase their chances of having a
common "rendezvous" basis where multiple LT trees can be bound together.
-Andy
--
Andy Green | TI Landing Team Leader
Linaro.org │ Open source software for ARM SoCs | Follow Linaro
http://facebook.com/pages/Linaro/155974581091106 -
http://twitter.com/#!/linaroorg - http://linaro.org/linaro-blog
_______________________________________________
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
