[build2] Forcibly using new revision

Per Edin per.edin at sequence-point.se
Wed Oct 10 19:25:40 UTC 2018

> In fact, I would probably go further and change the v1.12.0 tag
> to point to the v1.12.0+1 commit. Since a +N package is always
> assumed to be "better", I don't see a reason to keep the previous
> tag. But some might feel this is going a bit too far.

Thanks for the explanation! I solved it by removing the original v1.12.0
tag and creating a new tag pointing to the same commit as v1.12.0+1. Feels
better than removing it completely.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.build2.org/archives/users/attachments/20181010/dd971eba/attachment.html>

More information about the users mailing list