From: Jeff King <peff@peff.net>
To: Paul Brossier <piem@piem.org>
Cc: git@vger.kernel.org
Subject: Re: git not resuming push
Date: Wed, 23 Nov 2011 00:02:20 -0500 [thread overview]
Message-ID: <20111123050220.GA9127@sigill.intra.peff.net> (raw)
In-Reply-To: <4ECC6F80.6010907@piem.org>
On Tue, Nov 22, 2011 at 08:58:56PM -0700, Paul Brossier wrote:
> 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?
No, there isn't a way to resume just using push.
If you have shell access on the server, one workaround you can do is to
create a bundle with the commits in question, upload it via some
resumable protocol (like sftp, http, rsync, etc), possibly taking many
attempts, and then fetch the result on the server side from the bundle
into the repository.
See "git help bundle" for some examples.
-Peff
next prev parent reply other threads:[~2011-11-23 5:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-23 3:58 git not resuming push Paul Brossier
2011-11-23 5:02 ` Jeff King [this message]
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=20111123050220.GA9127@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=piem@piem.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).