On 5 December 2012 09:55, John Stultz john.stultz@linaro.org wrote:
So while I can try to update the linaro-android tree more frequently, maintaining that tree is more of a background task. So when my other commitments consume my attention, sometimes that update frequency is slower. Also, given we're already 3 releases beyond the AOSP tree, keeping the two branches in perfect sync is unlikely to happen (due to the higher chance of collisions). So if folks notice there is some critical functionality that is updated in the AOSP tree, when they let me know, I can be sure to merge it in (like was done with this case - albeit slower then I'd like).
That might be enough, i suppose.
However, if you're maintaining your own tree anyway, why not have Andrey pull your tree in addition to the current linaro-android-3.x-*rebase branch?
Since they are both contain a common subset, the merge will likely be quite easy. That way Andrey's tree will have a better chance of having the latest changes.
Does that seem ok?
That was the initial idea, but there were concerns from Tixy and Andrey on that. @Andrey: Do you want to comment again?
One other option, if someone has the cycles and interest, is that I would be fine with handing over the linaro-android tree maintenance responsibilities. If you or anyone else is interested, please send me email and we can work it out.
Not me atleast :) I am already maintaining few trees and they are killing my time like anything :) -- viresh