cgit/tests/t0001-validate-git-versions.sh, branch master

global: replace references to 'sha1' with 'oid'

2020-10-20T21:57:12Z

For some time now sha1 is considered broken and upstream is working to replace it with sha256. Replace all references to 'sha1' with 'oid', just as upstream does. Signed-off-by: Christian Hesse

tests: allow to skip git version tests

2020-01-13T20:17:19Z

This allows to run tests non-tagged git checkout or when bisecting. Signed-off-by: Christian Hesse

tests: successfully validate rc versions

2019-06-05T13:38:14Z

For testing versions the version string differs for git tag (v2.22.0-rc3) and tarball file name (2.22.0.rc3). Let's fix validation for testing versions. Signed-off-by: Christian Hesse

t0001: validate Git -rcN version numbers correctly

2013-04-27T15:21:22Z

When creating the GIT-VERSION-FILE that we use to test that the version of Git in git/ is the same as in the CGit Makefile, Git applies the transform "s/-/./g" to the version string. This doesn't affect released versions but does change RC version numbers such as 1.8.3-rc0. While CGit should only refer to a released Git version in general, it is useful to developers who want to test upcoming Git releases if the tests do work with RCs, so change t0001 to apply the same transform to our Makefile version before comparing it to the contents of GIT-VERSION-FILE. Signed-off-by: John Keeping

t0001: ignore ".dirty" suffix on Git version

2013-04-15T14:59:37Z

When testing modifications in Git that affect CGit, it is annoying to have t0001 failing simply because the Git version has a ".dirty" suffix when the version of Git there does indeed match that specified in the CGit makefile. Stop this by stripping the ".dirty" suffix from the GIT_VERSION variable. Note that this brings the "Git version" behaviour in line with the "submodule version" case which does not check if the working tree in git/ is modified. Signed-off-by: John Keeping

tests: use Git's test framework

2013-04-08T20:27:11Z

This allows tests to run in parallel as well as letting us use "prove" or another TAP harness to run the tests. Git's test framework requires Git to be fully built before letting any tests run, so add a new target to the top-level Makefile which builds all of Git instead of just libgit.a and make the "test" target depend on that. Signed-off-by: John Keeping

tests: check that Git version are in sync

2013-03-20T20:06:50Z

This ensures that the Git version pointed at by the submodule is the same as the one that will be fetched using "make get-git". Suggested-by: Ferry Huberts Signed-off-by: John Keeping