summaryrefslogtreecommitdiff
path: root/.github
diff options
context:
space:
mode:
authorpsakievich <psakiev@sandia.gov>2022-08-04 14:17:34 -0600
committerGitHub <noreply@github.com>2022-08-04 13:17:34 -0700
commit3b1401f2921d81740c2d17d96a3b25d7ecb4a299 (patch)
treed892a5bfd40eef17a3bd95935827af1434c514f6 /.github
parent19a8bb53f0e3c267f0eee7055f8041dff1f567d1 (diff)
downloadspack-3b1401f2921d81740c2d17d96a3b25d7ecb4a299.tar.gz
spack-3b1401f2921d81740c2d17d96a3b25d7ecb4a299.tar.bz2
spack-3b1401f2921d81740c2d17d96a3b25d7ecb4a299.tar.xz
spack-3b1401f2921d81740c2d17d96a3b25d7ecb4a299.zip
Git Ref versions can be paired to defined versions in the spec (#30998)
The current use of git ref's as a version requires a search algorithm to pick the right matching version based on the tags in the git history of the package. This is less than ideal for the use case where users already know the specific version they want the git ref to be associated with. This PR makes a new version syntax [package]@[ref]=[version] to allow the users to specify the exact hash they wish to use.
Diffstat (limited to '.github')
0 files changed, 0 insertions, 0 deletions