| commit | 328a43518244b970e1765eca78060bfeb265a584 | |
| author | Johannes Schindelin <johannes.schindelin@gmx.de> | |
| Wed, 24 Oct 2018 15:56:10 +0000 (24 08:56 -0700) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Thu, 25 Oct 2018 03:59:27 +0000 (25 12:59 +0900) | ||
| tree | 8f81d42f77bb7f4421e9507ebf62e91f4a1e7f38 | treesnapshot (tar.gz zip) |
| parent | cae598d9980661a978e2df4fb338518f7bf09572 | commitdiff |
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>
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>
| t/t5537-fetch-shallow.sh | diffblobblamehistory |