git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dennis Kaarsemaker <dennis@kaarsemaker.net>
To: Pirate Praveen <praveen@debian.org>
Cc: git@vger.kernel.org
Subject: Re: support git+mosh for unreliable connections
Date: Wed, 15 Apr 2015 15:45:21 +0200	[thread overview]
Message-ID: <1429105521.14175.0.camel@kaarsemaker.net> (raw)
In-Reply-To: <552E628C.7040809@debian.org>

On wo, 2015-04-15 at 18:37 +0530, Pirate Praveen wrote:
> Hi,
> 
>  When working with big projects over a slow, unreliable connection,
> currently there is no way to resume a clone or pull when the connection
> breaks. mosh is a better replacement for ssh over unreliable
> connections. supporting git+mosh protocol will go a long way in
> supporting people who work with unreliable, mobile networks, especially
> in developed countries (I personally have to try many times when working
> with large projects as my 3g mobile connection keeps dropping. I
> recently discovered mosh and it works like a charm. More about mosh
> https://mosh.mit.edu/

mosh isn't a generic transport though, it's a udp-based session state
synchronization protocol. I don't think it can be used as a git
transport.

-- 
Dennis Kaarsemaker
www.kaarsemaker.net

  reply	other threads:[~2015-04-15 13:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-15 13:07 support git+mosh for unreliable connections Pirate Praveen
2015-04-15 13:45 ` Dennis Kaarsemaker [this message]
2015-04-15 13:52 ` Michael J Gruber
2015-04-15 14:18   ` Pirate Praveen
2015-04-15 14:41     ` Johannes Schindelin
2015-04-15 15:33       ` Trevor Saunders
2015-04-15 17:46         ` Johannes Schindelin
2015-04-15 18:59           ` Trevor Saunders
2015-04-16  9:29             ` Michael J Gruber
2015-04-15 19:25           ` Dennis Kaarsemaker
2015-04-22  6:54             ` Andreas Krey
2015-04-15 14:22 ` Johannes Schindelin
2015-04-15 14:43   ` Pirate Praveen
2015-04-15 20:26     ` Ilari Liusvaara
2015-04-20  8:39       ` Pirate Praveen

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=1429105521.14175.0.camel@kaarsemaker.net \
    --to=dennis@kaarsemaker.net \
    --cc=git@vger.kernel.org \
    --cc=praveen@debian.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).