diff options
| author | fanquake <fanquake@gmail.com> | 2019-06-14 13:26:59 +0800 |
|---|---|---|
| committer | fanquake <fanquake@gmail.com> | 2019-06-14 13:38:52 +0800 |
| commit | 7524376a81a1955f4da4adb23005f2122b18a270 (patch) | |
| tree | 647c47ee4dffd802850e7831aaa1536f0f500157 /contrib/windeploy | |
| parent | 431d81b61ca968da2d7c25f0d56455a44cd46fed (diff) | |
| parent | 067fba56314f399674dd471c663e663040be52a3 (diff) | |
Merge #16201: devtools: Always use unabbreviated commit IDs in github-merge.py
067fba563 devtools: Always use unabbreviated commit IDs in github-merge.py (Wladimir J. van der Laan)
Pull request description:
Always put the unabbreviated commit IDs in the generated commit messages and other places. This prevents the developer's `core.abbrev` git setting from leaking through and is better against ambiguity too.
ACKs for commit 067fba:
MarcoFalke:
ACK 067fba56314f399674dd471c663e663040be52a3 (replaces `h` with `H`, didn't test)
promag:
ACK 067fba56314f399674dd471c663e663040be52a3, from the documentation https://git-scm.com/docs/pretty-formats:
fanquake:
ACK https://github.com/bitcoin/bitcoin/pull/16201/commits/067fba56314f399674dd471c663e663040be52a3. Tested by merging this PR into master, then merging a second PR ontop and checking that full commit hashes were being used. Also checked documentation linked to above. Did not check that this works when a different `core.abbrev` is set locally.
Tree-SHA512: a851d10490cd8bcd8bca29094b08a6b9f883cfe1b0767ccda7ca789e4c8eff6260a4d82c33cb3d9bab01dd30ac8c9100cb7adbcb1911bb399d9385c1e1f15ecd
Diffstat (limited to 'contrib/windeploy')
0 files changed, 0 insertions, 0 deletions