LBRY-Vault/contrib/build-linux
SomberNight f5f3394552
git sanity: enforce "git checkout commithash" actually pulls commit
If there is a collision between a branch name and a commit hash, git
will choose the branch, even if the full 40-hex-long commit hash is
given. GitHub disallows branches/tags with such a name but git itself
does not. By adding the `^{commit}` syntax sugar after a ref name,
we can tell git that we want the commit hash to be preferred,
and hence we don't need to trust GitHub (only git).

see https://security.stackexchange.com/questions/225411/
2020-06-16 19:55:17 +02:00
..
appimage git sanity: enforce "git checkout commithash" actually pulls commit 2020-06-16 19:55:17 +02:00
sdist sdist build: update message about reproducibility 2020-06-13 03:12:33 +02:00