From: Paul Brossier <piem@piem.org>
To: git@vger.kernel.org
Subject: git not resuming push
Date: Tue, 22 Nov 2011 20:58:56 -0700 [thread overview]
Message-ID: <4ECC6F80.6010907@piem.org> (raw)
Hi!
I'm trying to upload large amount of data from a connection that often
cuts.
If the connection fails after uploading part of the data, it seems I
need to start over from zero again. Is there a way to resume the upload
instead?
Here is an example:
$ git push
Counting objects: 504, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (475/475), done.
Write failed: Broken pipe1/476), 533.78 MiB | 60 KiB/s
fatal: The remote end hung up unexpectedly
error: pack-objects died of signal 13
error: failed to push some refs to 'myhost.org:/git/myrepo/'
$ git push
Counting objects: 504, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (475/475), done.
Writing objects: 12% (61/476), 89.34 MiB | 23 KiB/s
Thanks, piem
next reply other threads:[~2011-11-23 4:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-23 3:58 Paul Brossier [this message]
2011-11-23 5:02 ` git not resuming push Jeff King
2011-11-23 6:24 ` Junio C Hamano
2011-11-23 17:25 ` Paul Brossier
2011-11-23 18:46 ` Jeff King
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=4ECC6F80.6010907@piem.org \
--to=piem@piem.org \
--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).