kicad-developers team mailing list archive

[John Beard <john.j.beard@xxxxxxxxx>]

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
<js.reynaud@xxxxxxxxx> wrote:
> 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 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 regression arises between one nightly and the next, the
>> date only approximately tells you where to start bisecting.
>>
>> The Bzr-style rev number is almost entirely useless especially when
>> the build is also tagged with a date, and Bzr is dead and gone.
>> Date+git rev give you both an incrementing number for quick
>> comparisons of age of build, and the git commit is an unambiguous
>> pointer to the exact commit.
>>
>> Nearly all "nightly" and "git tracker" pacakges (PPA, AUR, etc) put
>> the git hash in the build number, pretty much for this exact reason.
>>
>> Cheers,
>>
>> John
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp