Re: [Kicad-developers] Ubuntu build commit IDs

Hi Jean-Samuel, Thank you, a bug report on a nightly now is tagged no-vcs-found-be10de8~57~ubuntu16.10.1, which is much clearer! Cheers, John On Mon, Feb 27, 2017 at 8:22 PM, Jean-Samuel Reynaud wrote: > Hi all, > > In your example 7735 is the revno form the git repo (It is not related > to bz

Re: [Kicad-developers] Ubuntu build commit IDs

Hi all, In your example 7735 is the revno form the git repo (It is not related to bzr). I had changed it with the git-commit keywork. I should be useful. Le 26/02/2017 à 16:46, John Beard a écrit : > Hi, > > Would it be possible to get the ubuntu builds tagged with a commit > hash? Version strin

Re: [Kicad-developers] Ubuntu build commit IDs

*Please*. I'm tired of people asking for support and making me figure out what "7735" is. We left bzr a long time ago now. On Sun, Feb 26, 2017 at 11:46:09PM +0800, John Beard wrote: > Hi, > > Would it be possible to get the ubuntu builds tagged with a commit > hash? Version strings like 2017022

[Kicad-developers] Ubuntu build commit IDs

Hi, Would it be possible to get the ubuntu builds tagged with a commit hash? Version strings like 201702251416+7735~57~ubuntu16.10.1 are not very useful if you want to know exactly which commit a build relates to. The exact commit is very useful when looking at a bug report from a nightly. If a