On 2016, ജൂൺ 7 9:16:01 PM IST, Stefan Beller wrote:
>On Tue, Jun 7, 2016 at 8:43 AM, Stefan Beller
>wrote:
>> (Are you telling me that patch is faulty?)
>
>The patch is not part of v2.8.1 but part of v2.8.3,
>so take a later version, or cherry-pick that
On Tuesday 07 June 2016 04:00 PM, Johannes Schindelin wrote:
> Hi Pirate Praveen,
>
> On Tue, 7 Jun 2016, Pirate Praveen wrote:
>
>> I'm trying to rebuild git 2.8.1 on debian jessie/stable and I get this
>> error (tests upto this succeeds).
>>
>> not ok
Hi,
I'm trying to rebuild git 2.8.1 on debian jessie/stable and I get this
error (tests upto this succeeds).
not ok 32 - should avoid cleaning possible submodules
I added debian stretch repo to apt sources.list and ran apt-get source
-b git.
You can see the build options passed here
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 user
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
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
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 the
7 matches
Mail list logo