From: Junio C Hamano <junkio@cox.net>
Date: Tue, 25 Oct 2005 17:17:20 GMT
Subject: Re: How to clone faster via ssh ?
Message-ID: <7vbr1dh5y7.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <Pine.LNX.4.63.0510251103110.24174@wbgn013.biozentrum.uni-wuerzburg.de>

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

> On Tue, 25 Oct 2005, Alexander Litvinov wrote:
>
>> Forgot to tell:
>> clone via ssh was made using this command:
>> time git-clone -n ssh://lan@lan/home/lan/tmp/git/billing/repo r3
>
> If you have a working git on the other side, you could do
>
> 	time git-clone lan@lan:/home/lan/tmp/git/billing/repo r3
>
> which would utilize git-clone-pack. Way faster.

I think both of these notations do the same.

The time to unpack the resulting pack on this end is eliminated
if you use git from last week, namely this commit:

commit e1c7ada6dd1fdf249d0bb84f3293d3be768b9239
Author: Junio C Hamano <junkio@cox.net>
Date:   Wed Oct 19 14:43:43 2005 -0700

    git-clone: always keep pack sent from remote.

    This deprecates --keep and -q flags and always keeps the
    pack
    sent from the remote site.  Corresponding configuration
    variables are also removed.

    Signed-off-by: Junio C Hamano <junkio@cox.net>

But you would still pay for creating a pack on the remote side.