Hello Nicolas, On Wed, 13 Jul 2011 08:22:08 +0200 "Dechesne, Nicolas" <n-deche...@ti.com> wrote:
> On Tue, Jul 12, 2011 at 9:07 AM, Ricardo Salveti > <ricardo.salv...@linaro.org > > wrote: > > > Is there other way to fix this at the tool instead of forcing the > > component tree owner to not rebase the tree? > > > > if the problem is that you rely on external maintainers to 1) create > a tag or a ref that reaches the commits you depend on for your > release, or 2) do not rebase so that you don't loose your commit. > it's likely that the only option is to mirror all trees you need so > that you can tag them and have no external dependency. that's one of > the reason why all projects are cloned on git.omapzoom.org, because > we needed to get reproducible trees since OMAP Android releases are > also based on 'static' manifests Well, yes, mirroring everything of course will be the most general solution, but would add burden on our side and complicate getting quick answer to the most basic question "what was changed in Linaro tree comparing to the upstream". So, while we're busy with setting up the rest of Android-related infrastructure, maybe it's worth trying to optimize existing set up even if it's heuristical and depends on some external conditions, maybe it will be quite workable in practice after all. -- Best Regards, Paul Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog _______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
