git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git not resuming push

From
Junio C Hamano <gitster@pobox.com>
Date
Nov 23, 2011, 06:24 UTC
Message-ID
<7vmxbncq5v.fsf@alter.siamese.dyndns.org>
In-Reply-To
<20111123050220.GA9127@sigill.intra.peff.net>
Jeff King <peff@peff.net> writes:
Show 15 quoted lines
> 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.

Another possibility, if it is the connection between you and the other side that is the problem, is to chunk your push in smaller pieces. That is, if you are trying to push out v3.0, you first push only to v1.0, then to v2.0, and then finally to v3.0.

Peff, by the way, wouldn't this request reminds of us of a scenario we discussed recently, which I said I would imagine would be common while you dismissed as not likely to be common?

Previous: Jeff KingNext: Paul Brossier
Message 3 of 5 in “git not resuming push”
  1. Paul BrossierNov 23, 2011
  2. Jeff KingNov 23, 2011
  3. Junio C HamanoNov 23, 2011
  4. Paul BrossierNov 23, 2011
  5. Jeff KingNov 23, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.