From: Tim Visher <tim.visher@gmail.com>
To: Git Mailing List <git@vger.kernel.org>
Subject: `git (submodule update|fetch|pull) --continue` similar to `curl -C -`?
Date: Mon, 12 Apr 2010 11:00:52 -0400 [thread overview]
Message-ID: <u2lc115fd3c1004120800y54d09b8bt3e7aeda9509703c8@mail.gmail.com> (raw)
Hey All,
I'm behind a very aggressive firewall/proxy at work and as far as I
can tell it actually interrupts long connections on purpose. Most
programs seem to be able to deal with it, although the connection
speed is slower. Git, however, seems to not be able to deal with it
every once and awhile.
For instance:
$ g sm update
Initialized empty Git repository in /home/tim/.emacs.d/site-lisp/ecb/.git/
error: Unable to get pack file
http://github.com/emacsmirror/ecb.git/objects/pack/pack-364b879fac4ebed663f528dc3ddff99ddd6716e9.pack
***emphasis***
transfer closed with 969832 bytes remaining to read
***emphasis***
error: Unable to find 67861e756712c4e5917461e8b149089dceceec88
under http://github.com/emacsmirror/ecb.git
Cannot obtain needed object 67861e756712c4e5917461e8b149089dceceec88
while processing commit 8043b271a679c7faae65c0d75a73e63bb25d1620.
error: Fetch failed.
Clone of 'http://github.com/emacsmirror/ecb.git' into submodule
path 'site-lisp/ecb' failed
It would seem like an interesting idea to be able to download a repo
progressively with interruptions along the lines of `curl -C -` so
that if an interruption happened you can still report the error but
then offer a `--continue` or `--abort` option. --continue would
obviously attempt to pick up where it left off and --abort would
delete the cache to save the disk space.
Thoughts?
This could also be a problem with GitHub. I don't know enough about
submodules to make an educated guess there. I only guess that it's
the proxy's fault because I only experience this at work.
--
In Christ,
Timmy V.
http://burningones.com/
http://five.sentenc.es/ - Spend less time on e-mail
reply other threads:[~2010-04-12 15:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=u2lc115fd3c1004120800y54d09b8bt3e7aeda9509703c8@mail.gmail.com \
--to=tim.visher@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).