W/in chrome-os, we don't use clone.bundle currently. If you ctrl+c at just the
right time (best I can tell, during repo selfupdate itself) it'll result in
repo leaving behind a zero length clone.bundle file.
All later Sync_NetworkHalf invocations will spot this file, and try to invoke
`git fetch empty-bundle`; git (at least versions 1.7.8.{1,2}) will go into an
infinite loop trying to read it and failing, leaving the user to either find
that file and remove it, or do a checkout from scratch.
While that misbehavior needs fixing in git, we shouldn't be creating those
files anyways in repo, as such add protection code that detects it and cleans
it.
Original issue reported on code.google.com by ferri...@chromium.org on 3 Jan 2012 at 12:18
Original issue reported on code.google.com by
ferri...@chromium.orgon 3 Jan 2012 at 12:18Attachments: