search for: grev

> On Jun 30, 2016, at 4:14 PM, Renato Golin via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > > On 30 Jun 2016 10:20 p.m., "Robinson, Paul" <paul.robinson at sony.com <mailto:paul.robinson at sony.com>> wrote: > > We've since stopped creating the tags, and gotten used to not having > > them. We do the 'rev-list --count' trick

...$HASH > > 3. Convert revision number $NUM to git hash: > git rev-list HEAD | tail -n $NUM | head -n 1 I just want to point out another alternative that I often use in my projects: (Example from buildbot repo I had handy) $ git describe v0.9.0b8-579-ge06cac6 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...

On 30 Jun 2016 10:20 p.m., "Robinson, Paul" <paul.robinson at sony.com> wrote: > We've since stopped creating the tags, and gotten used to not having > them. We do the 'rev-list --count' trick which mainly gets recorded as > one component of the version number, and it has been working for us. Does that work for sub modules inside the umbrella project? How