{"thread":{"id":"23430","subject":"`git (submodule update|fetch|pull) --continue` similar to `curl -C -`?","startedAt":"2010-04-12T15:00:52Z","lastAt":"2010-04-12T15:00:52Z","messageCount":1,"participants":["Tim Visher"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"139342","messageId":"u2lc115fd3c1004120800y54d09b8bt3e7aeda9509703c8@mail.gmail.com","threadId":"23430","inReplyTo":null,"subject":"`git (submodule update|fetch|pull) --continue` similar to `curl -C -`?","fromName":"Tim Visher","fromEmail":"tim.visher@gmail.com","sentAt":"2010-04-12T15:00:52Z","receivedAt":"2010-04-12T15:00:52Z","isPatch":false,"sender":{"key":"tim.visher@gmail.com","avatar":"https://gravatar.com/avatar/98307ce54bcac1a46b5d845827d5386e2a27895ff08790cdd3877ad527760575?d=mp&s=160"},"body":"Hey All,\n\nI'm behind a very aggressive firewall/proxy at work and as far as I\ncan tell it actually interrupts long connections on purpose.  Most\nprograms seem to be able to deal with it, although the connection\nspeed is slower.  Git, however, seems to not be able to deal with it\nevery once and awhile.\n\nFor instance:\n\n    $ g sm update\n    Initialized empty Git repository in /home/tim/.emacs.d/site-lisp/ecb/.git/\n    error: Unable to get pack file\nhttp://github.com/emacsmirror/ecb.git/objects/pack/pack-364b879fac4ebed663f528dc3ddff99ddd6716e9.pack\n    ***emphasis***\n    transfer closed with 969832 bytes remaining to read\n    ***emphasis***\n    error: Unable to find 67861e756712c4e5917461e8b149089dceceec88\nunder     http://github.com/emacsmirror/ecb.git\n    Cannot obtain needed object 67861e756712c4e5917461e8b149089dceceec88\n    while processing commit 8043b271a679c7faae65c0d75a73e63bb25d1620.\n    error: Fetch failed.\n    Clone of 'http://github.com/emacsmirror/ecb.git' into submodule\npath     'site-lisp/ecb' failed\n\nIt would seem like an interesting idea to be able to download a repo\nprogressively with interruptions along the lines of `curl -C -` so\nthat if an interruption happened you can still report the error but\nthen offer a `--continue` or `--abort` option.  --continue would\nobviously attempt to pick up where it left off and --abort would\ndelete the cache to save the disk space.\n\nThoughts?\n\nThis could also be a problem with GitHub.  I don't know enough about\nsubmodules to make an educated guess there.  I only guess  that it's\nthe proxy's fault because I only experience this at work.\n\n-- \n\nIn Christ,\n\nTimmy V.\n\nhttp://burningones.com/\nhttp://five.sentenc.es/ - Spend less time on e-mail\n"}]}