Tree:
fcbc1c9a45
2.9.x
283
3.0.x
3.1
3.2.x
3.3.3.1
bip39-recovery
coincointrol-statusbar
dependabot/pip/contrib/deterministic-build/ecdsa-0.13.3
hard-fail-on-bad-server-string
ln-negative-red
master
password_lineedit
patch-1
patch-2
patch-3
patch-4
regtest_lnd
seed_v14
sqlite_db
ssl-fingerprint-check
0.56
0.57
0.57a
0.57b
0.57c
0.58
0.59
0.59a
0.59b
0.60
0.61-r1
0.61b
1.1
1.2
1.3
1.5
1.5.1
1.5.2
1.5.3
1.5.4
1.5.5
1.5.6
1.5.7
1.5.8
1.6.0
1.6.1
1.6.2
1.7
1.7.1
1.7.2
1.7.3
1.7.4
1.7rc0
1.8
1.8.1
1.9
1.9.1
1.9.2
1.9.3
1.9.4
1.9.5
1.9.6
1.9.7
1.9.8
2.0
2.0-beta
2.0.1
2.0.2
2.0.3
2.0.4
2.0b2
2.0b3
2.1
2.1.1
2.2
2.3
2.3.1
2.3.2
2.3.3
2.4
2.4.1
2.4.2
2.4.3
2.5
2.5.1
2.5.2
2.5.3
2.5.4
2.6
2.6.1
2.6.2
2.6.3
2.6.4
2.7.0
2.7.1
2.7.10
2.7.11
2.7.12
2.7.13
2.7.14
2.7.15
2.7.16
2.7.17
2.7.18
2.7.2
2.7.3
2.7.4
2.7.5
2.7.6
2.7.7
2.7.8
2.7.9
2.8.0
2.8.1
2.8.2
2.8.3
2.9.0
2.9.1
2.9.2
2.9.3
2.9.4
3.0.0
3.0.1
3.0.2
3.0.3
3.0.4
3.0.5
3.0.6
3.1.0
3.1.1
3.1.2
3.1.3
3.2.0
3.2.1
3.2.2
3.2.3
3.2.4
3.3.0
3.3.1
3.3.2
3.3.3
3.3.4
3.3.5
3.3.6
3.3.7
3.3.8
password_v2
seed_v10
seed_v5
seed_v7
seed_v8
seed_v9
${ noResults }
2 Commits (fcbc1c9a459d79d54d6c102912f56b922d58fb19)
| Author | SHA1 | Message | Date |
|---|---|---|---|
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/
|
5 years ago |
ThomasV
|
485422b072 |
move android stuff to contrib/android
|
5 years ago |