You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After running git gc cmake may fail to configure the build. git gc deleted the file .git/refs/head/merge-2.067 (my current branch) and moved the reference into file .git/packed-refs. This file is not parsed for the reference.
Solution is (a) parse .git/packed-refs if ref is not found or (b) use
git rev-parse --symbolic-full-name HEAD
to get the reference and
git show-ref --hash ${HEAD_REF}
to get the hash. The only challenge is how to run these commands at every build (like the original implementation).
The text was updated successfully, but these errors were encountered:
After running `git gc` cmake may fail to configure the build.
`git gc` deleted the file `.git/refs/head/merge-2.067` (my current branch) and
moved the reference into file `.git/packed-refs`. This file is not parsed for
the reference.
Solution is (a) parse `.git/packed-refs` if ref is not found or (b) use
git rev-parse --symbolic-full-name HEAD
to get the reference and
git show-ref --hash ${HEAD_REF}
to get the hash.
This commits uses solution (a).
The problem from issue #874 has another variant:
If .git/logs/refs/heads/merge-2.067 exists then this ref is
returned as hash value(!). This is plain wrong. Solution is
again to look up `.git/packed-refs`.
After running
git gc
cmake may fail to configure the build.git gc
deleted the file.git/refs/head/merge-2.067
(my current branch) and moved the reference into file.git/packed-refs
. This file is not parsed for the reference.Solution is (a) parse
.git/packed-refs
if ref is not found or (b) useto get the reference and
to get the hash. The only challenge is how to run these commands at every build (like the original implementation).
The text was updated successfully, but these errors were encountered: