[PATCH 0/4] Recovery after interrupted HTTP(s) fetch

[Sergey Vlasov <vsu@altlinux.ru>]

[-- Attachment #1: Type: text/plain, Size: 1431 bytes --]

Hello!

The current implementation of git-http-fetch, git-local-fetch,
git-ssh-fetch has a problem: if a fetch was interrupted in the middle,
some objects in the local repository will be missing, and there is no
easy way to recover.  If you just attempt to repeat the fetch, it will
notice that you already have the most recent commit object, and will
not fetch anything more - the repository will stay broken.  Seems that
the only way to go forward is to prune the repository (which will
remove the fetched objects, because they are not referenced) and
repeat the fetch again from the beginning, but this is obviously
wasteful.

The problem is caused by the behavior of fetch.c:process_commit() - it
skips parent commits which already exist locally.  This is a good
optimization if your repository is OK, but after an interrupted fetch
there will be some missing objects in the object tree; the only way to
find them is to scan the whole tree, so stopping at the existing
commits is wrong.

This set of patches adds the recovery mode to git-*-fetch and the
git-fetch script, which is enabled by the --recover option; in this
mode the program will walk through the whole object tree and try to
download any missing objects.  Obviously, this could take some time,
but it is better than throwing away all already fetched objects after
an error in the middle of a long fetch operation.

-- 
Sergey Vlasov

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]