On Mon, 29 Aug 2011 12:15:15 -0500 Zach Pfeffer <zach.pfef...@linaro.org> wrote:
[] > >> We could probably just update the branch after the automerge step. > > What do you mean "SHA1 reachability"? I can "reach" arbitrary > > HEADs using a hash even if they're not tagged so long as I didn't > > garbage collect. If I tagged them they're guaranteed to not be > > garbage collected. I can always "reach" them for checkout. So > > what is this "reachability" issue? > > > > The way Paul described it, it sounds like a limitation with this > > repo script that it depends on specifically a branch has been > > checked out. > > All repo is doing with a pinned-manifest.xml is: > > foreach git in this manifest > checkout sha1 > > so as long as you can checkout the sha1 everything is cool. The reason > we're using this is because we can automatically create a manifest > with the sha1's of every sub git head that we built. This allows > someone to reproduce the build exactly and allows us to ship what we > test. If you can apply the same tag across all gits, which we can do > now, and that'll keep the sha's around than that's what we should do. Yes, and we also should use *that tag* in the manifest! > > >>> Is it perhaps possible to improve "repo" instead? > > > > -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 > > -- 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
