On Wed, 15 Apr 2015 21:25:44 +, Dennis Kaarsemaker wrote:
...
> It does not and cannot work. The way mosh works, is that it uses ssh to
> log in and launch a mosh-server daemon. This daemon and the mosh client
> then communicate via a custom UDP protocol. The SSH connection is closed
> after th
On Thursday 16 April 2015 01:56 AM, Ilari Liusvaara wrote:
> On Wed, Apr 15, 2015 at 08:13:51PM +0530, Pirate Praveen wrote:
>>
>> Q: Are the mosh principles relevant to other network applications?
>>
>> We think so. The design principles that Mosh stands for are
>> conservative: warning the us
Trevor Saunders venit, vidit, dixit 15.04.2015 20:59:
> On Wed, Apr 15, 2015 at 07:46:15PM +0200, Johannes Schindelin wrote:
>> Hi Trevor,
>>
>> On 2015-04-15 17:33, Trevor Saunders wrote:
>>> On Wed, Apr 15, 2015 at 04:41:42PM +0200, Johannes Schindelin wrote:
On 2015-04-15 16:18, Pirate
On Wed, Apr 15, 2015 at 08:13:51PM +0530, Pirate Praveen wrote:
>
> Q: Are the mosh principles relevant to other network applications?
>
> We think so. The design principles that Mosh stands for are
> conservative: warning the user if the state being displayed is out of
> date, serializing an
On wo, 2015-04-15 at 19:46 +0200, Johannes Schindelin wrote:
> On 2015-04-15 17:33, Trevor Saunders wrote:
> > but it certainly does support ssh
> > and then doing IO.
>
Yes, in interactive sessions. mosh synchronizes terminal state, it
doesn't allow random I/O between client and server.
> Ah,
On Wed, Apr 15, 2015 at 07:46:15PM +0200, Johannes Schindelin wrote:
> Hi Trevor,
>
> On 2015-04-15 17:33, Trevor Saunders wrote:
> > On Wed, Apr 15, 2015 at 04:41:42PM +0200, Johannes Schindelin wrote:
> >>
> >> On 2015-04-15 16:18, Pirate Praveen wrote:
> >> > On Wednesday 15 April 2015 07:22 PM
Hi Trevor,
On 2015-04-15 17:33, Trevor Saunders wrote:
> On Wed, Apr 15, 2015 at 04:41:42PM +0200, Johannes Schindelin wrote:
>>
>> On 2015-04-15 16:18, Pirate Praveen wrote:
>> > On Wednesday 15 April 2015 07:22 PM, Michael J Gruber wrote:
>> >> What would that require git to do, beyond taking wh
On Wed, Apr 15, 2015 at 04:41:42PM +0200, Johannes Schindelin wrote:
> Hi Praveen,
>
> On 2015-04-15 16:18, Pirate Praveen wrote:
> > On Wednesday 15 April 2015 07:22 PM, Michael J Gruber wrote:
> >> What would that require git to do, beyond taking whatever you tell it
> >> (using GIT_SSH or _GIT_
On Wednesday 15 April 2015 07:52 PM, Johannes Schindelin wrote:
> From https://github.com/keithw/mosh:
>
>> Mosh does not support X forwarding or the non-interactive uses of SSH,
>> including port forwarding.
>
> In particular it "does not support [...] the non-interactive uses of SSH",
> which
Hi Praveen,
On 2015-04-15 16:18, Pirate Praveen wrote:
> On Wednesday 15 April 2015 07:22 PM, Michael J Gruber wrote:
>> What would that require git to do, beyond taking whatever you tell it
>> (using GIT_SSH or _GIT_SSH_COMMAND) to use as a drop in replacement for ssh?
>
> May be support git+mos
Hi Praveen "A",
On 2015-04-15 15:07, Pirate Praveen wrote:
> 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 g
On Wednesday 15 April 2015 07:22 PM, Michael J Gruber wrote:
> What would that require git to do, beyond taking whatever you tell it
> (using GIT_SSH or _GIT_SSH_COMMAND) to use as a drop in replacement for ssh?
>
> Michael
>
May be support git+mosh as a protocol, since it is not a drop in
repla
Pirate Praveen venit, vidit, dixit 15.04.2015 15:07:
> 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+
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 g
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 wi
15 matches
Mail list logo
