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

Re: git not resuming push

From
Jeff King <peff@peff.net>
Date
Nov 23, 2011, 18:46 UTC
Message-ID
<20111123184614.GA21146@sigill.intra.peff.net>
In-Reply-To
<7vmxbncq5v.fsf@alter.siamese.dyndns.org>
On Tue, Nov 22, 2011 at 10:24:12PM -0800, Junio C Hamano wrote:
Show 8 quoted lines
> 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?

I didn't say it wasn't common; I said I didn't think it was the majority case, and that I didn't want a solution that only helped this case without covering the other cases.

Also, it isn't clear to me that an immediate-reconnect scheme would work. When the connection gets dropped, is it simply that TCP connection that goes out, and another one could immediately be made to resume? Or is the network actually out (even if only for a few seconds)?

-Peff
Previous: Paul Brossier
Message 5 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.