On Tue, Nov 22, 2011 at 10:24:12PM -0800, Junio C Hamano wrote: > 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 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html