summaryrefslogtreecommitdiff
path: root/t/t6301-for-each-ref-errors.sh
diff options
context:
space:
mode:
authorLibravatar Johannes Schindelin <johannes.schindelin@gmx.de>2018-10-24 08:56:10 -0700
committerLibravatar Junio C Hamano <gitster@pobox.com>2018-10-25 12:59:27 +0900
commit328a43518244b970e1765eca78060bfeb265a584 (patch)
tree8f81d42f77bb7f4421e9507ebf62e91f4a1e7f38 /t/t6301-for-each-ref-errors.sh
parentGit 2.19.1 (diff)
downloadtgif-328a43518244b970e1765eca78060bfeb265a584.tar.xz
repack: point out a bug handling stale shallow info
A `git fetch --prune` can turn previously-reachable objects unreachable, even commits that are in the `shallow` list. A subsequent `git repack -ad` will then unceremoniously drop those unreachable commits, and the `shallow` list will become stale. This means that when we try to fetch with a larger `--depth` the next time, we may end up with: fatal: error in object: unshallow <commit-hash> Reported by Alejandro Pauly. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t6301-for-each-ref-errors.sh')
0 files changed, 0 insertions, 0 deletions