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
Not sure this is something that should be fixed by dune, but am opening the issue just to put it out: dune subst calls git describe, but the number of digits used in the "short hash" depends on the version of git as far as I can see. Recently I was bitten by this where the same commit built under Unix (Ubuntu 18.04) and Windows (Cygwin) ended up with different strings substituted.
git describe accepts a --abbrev=<n> argument to specify how many digits to use in the short hash, but it is not clear that using this is the right thing to do.
The text was updated successfully, but these errors were encountered:
Not sure this is something that should be fixed by
dune
, but am opening the issue just to put it out:dune subst
callsgit describe
, but the number of digits used in the "short hash" depends on the version ofgit
as far as I can see. Recently I was bitten by this where the same commit built under Unix (Ubuntu 18.04) and Windows (Cygwin) ended up with different strings substituted.git describe
accepts a--abbrev=<n>
argument to specify how many digits to use in the short hash, but it is not clear that using this is the right thing to do.The text was updated successfully, but these errors were encountered: