diff options
author | William Gathoye | 2017-08-14 01:37:52 +0200 |
---|---|---|
committer | William Gathoye | 2017-08-14 01:37:52 +0200 |
commit | e4972e168d6706ef4e25bbb21e7170e40e67ab0d (patch) | |
tree | df55c9ff58b11343035d8cb52afdbc3e84e955f6 /.SRCINFO | |
parent | c49d7dc73fa1183620db30f639a0da524caa8c9b (diff) | |
download | aur-e4972e168d6706ef4e25bbb21e7170e40e67ab0d.tar.gz |
The commit id was always the same, fix this.
We previously used a way to recover the last tag from all branches.
However proceeding this way could leads in unattended behaviors.
First, imagine we are in the release 4.0, and a bug fix appears for 3.6
afterwardsi. The latest tag is not 4.0.x but 3.6.x and the package is not
updated.
Second, the manner we were taking the tag was taking its fixed commit with
it, not the latest commit available after the tag.
Now, we are just using a more common manner to recover the commit id: we
are prefixing it with the latest tag reachable from the **current** branch.
Diffstat (limited to '.SRCINFO')
0 files changed, 0 insertions, 0 deletions