diff options
| author | Patrick Steinhardt <psteinhardt@gitlab.com> | 2021-12-01 17:47:35 +0300 |
|---|---|---|
| committer | Patrick Steinhardt <psteinhardt@gitlab.com> | 2021-12-01 18:20:04 +0300 |
| commit | 755302945822f7caaf694f0b0b203aebc378d9af (patch) | |
| tree | 55dd8df62fab877a4f9583fa82bda3d89d072f26 /Makefile | |
| parent | f275c972fa02faf0caa9b021f3c42e22becba8f5 (diff) | |
Makefile: Silence git-fsck's dangling object output
After cloning test repos, we replace their references with our own
vision of references by removing all loose ones and moving in a
pre-packed packed-refs file. As a result, we get a bunch of dangling
objects because we effectively move back the repository in time even
though we already downloaded all objects. While not bad per-se, it
creates quite some output when we run git-fsck(1) to check the repo for
consistency.
Silence these messages by adding the `--no-dangling` switch.
Diffstat (limited to 'Makefile')
| -rw-r--r-- | Makefile | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -630,14 +630,14 @@ ${TEST_REPO}: ${Q}rm -rf $@/refs ${Q}mkdir -p $@/refs/heads $@/refs/tags ${Q}cp ${SOURCE_DIR}/_support/gitlab-test.git-packed-refs $@/packed-refs - ${Q}${GIT} -C $@ fsck --no-progress + ${Q}${GIT} -C $@ fsck --no-progress --no-dangling ${TEST_REPO_GIT}: ${GIT} clone --bare ${GIT_QUIET} https://gitlab.com/gitlab-org/gitlab-git-test.git $@ ${Q}rm -rf $@/refs ${Q}mkdir -p $@/refs/heads $@/refs/tags ${Q}cp ${SOURCE_DIR}/_support/gitlab-git-test.git-packed-refs $@/packed-refs - ${Q}${GIT} -C $@ fsck --no-progress + ${Q}${GIT} -C $@ fsck --no-progress --no-dangling ${BENCHMARK_REPO}: ${GIT} clone --bare ${GIT_QUIET} https://gitlab.com/gitlab-org/gitlab.git $@ |