Tracking Android kernel tips and Android builds
james.westby at canonical.com
Wed Aug 31 00:09:54 UTC 2011
On Tue, 30 Aug 2011 11:10:10 -0500, Zach Pfeffer <zach.pfeffer at linaro.org> wrote:
> There's no reason to do it now, because its solving the wrong problem.
> The problem is sha's disappear. We use sha's because the provide
> immovable references to the state of a set of git trees so that people
> can reproduce builds exactly. We don't need the change to tag a build
> after its been deemed correct, we just need to implement a function to
> tag across the gits so that all the shas continue to exist.
I'm sorry, but I'm not sure what course of action you are advocating
It sounds like you are advocating using a model where we use tags to
ensure that the referenced revisions are reachable from a head, and then
refer to the sha ids of the revisions in the manifest. Is that correct?
More information about the linaro-dev