<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><br class=""></div><div><blockquote type="cite" class=""><div class="">El jun. 30, 2016, a las 19:31, Matthias Braun via cfe-dev <<a href="mailto:cfe-dev@lists.llvm.org" class="">cfe-dev@lists.llvm.org</a>> escribió:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=us-ascii" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Jun 30, 2016, at 4:14 PM, Renato Golin via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" class="">llvm-dev@lists.llvm.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><p dir="ltr" class=""><br class="">
On 30 Jun 2016 10:20 p.m., "Robinson, Paul" <<a href="mailto:paul.robinson@sony.com" class="">paul.robinson@sony.com</a>> wrote:<br class="">
> We've since stopped creating the tags, and gotten used to not having<br class="">
> them. We do the 'rev-list --count' trick which mainly gets recorded as<br class="">
> one component of the version number, and it has been working for us.</p><p dir="ltr" class="">Does that work for sub modules inside the umbrella project?</p></div></blockquote><blockquote type="cite" class=""><div class=""><p dir="ltr" class="">How can you trigger a hook in the umbrella project for commits inside the sub modules? </p></div></blockquote><div class="">First: This is purely about generating sequential revision numbers, it does not help setting up a server hook to update the submodule references in the meta repository. The point I am trying to make here is that we only need to solve the problem of updating the submodule references, and that generating sequential ID numbers as an alternative to git hashes is no problem.</div><div class=""><br class=""></div><div class="">As far as I can see we need the following operations for sequential ID numbers and they are all easy enough to perform with git on the client side:</div><div class=""><br class=""></div><div class="">1. Produce revision number for current checkout (to use in tool --version output):</div><div class="">You can put something like</div><div class=""> > echo "#define VERSION $(git rev-list --count HEAD)" > version.h</div><div class="">in your buildsystem</div><div class=""><br class=""></div><div class="">2. Convert git hash to revision number:</div><div class=""> git rev-list --count $HASH</div><div class=""><br class=""></div><div class="">3. Convert revision number $NUM to git hash:</div><div class=""> git rev-list HEAD | tail -n $NUM | head -n 1</div></div></div></div></blockquote><br class=""></div><div>I just want to point out another alternative that I often use in my projects: (Example from buildbot repo I had handy)</div><div><br class=""></div><div>$ git describe</div><div><div>v0.9.0b8-579-ge06cac6</div><div><br class=""></div><div>The format is "TAG-N-gREV", where TAG is the closest reachable git tag in the past ("v0.9.0b8"), N is the relative number of revisions past that tag (579), and REV is the short revision to make it unique and easy to locate ("e06cac6", the 'g' is a literal character that prefixes the revision). In other words, that "-579-" represents a monotonically increasing value relative to the named tag and might serve your purposes. </div><div><br class=""></div><div>Jared</div></div><br class=""></body></html>