summaryrefslogtreecommitdiffstats
path: root/Utilities/.gitattributes
diff options
context:
space:
mode:
authorCraig Scott <craig.scott@crascit.com>2021-05-09 02:33:16 (GMT)
committerCraig Scott <craig.scott@crascit.com>2021-05-09 02:33:16 (GMT)
commit5e941a545bf5882ddf101cad383dc815fb651f26 (patch)
treeae3f6b468a3cfb2c8fec86eba4c6455b104521aa /Utilities/.gitattributes
parentfdbb5a599fc373a1ec7dbbfdcca34ff9669f3c48 (diff)
downloadCMake-5e941a545bf5882ddf101cad383dc815fb651f26.zip
CMake-5e941a545bf5882ddf101cad383dc815fb651f26.tar.gz
CMake-5e941a545bf5882ddf101cad383dc815fb651f26.tar.bz2
ExternalProject: Ensure git fetch if updating to hash we don't have yet
In ac6a4d4884 (ExternalProject: Improve robustness of update step, 2020-10-17), the method used to check whether we already have a commit or not was changed from using git rev-list to git rev-parse. The new logic assumed rev-parse would output nothing if given a commit hash it didn't know about, but it simply prints the hash again without raising an error in this scenario. Amend that logic by adding ^{commit} to the ref to ensure we do get an error if that ref is not currently known. Fixes: #22166
Diffstat (limited to 'Utilities/.gitattributes')
0 files changed, 0 insertions, 0 deletions