From: Alexander Litvinov <lan@ac-sw.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: How to clone faster via ssh ?
Date: Tue, 25 Oct 2005 18:30:24 +0700 [thread overview]
Message-ID: <200510251830.24550.lan@ac-sw.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0510251103110.24174@wbgn013.biozentrum.uni-wuerzburg.de>
> 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 have tried this command:
lan@lan> time git-clone lan@lan:/home/lan/tmp/git/billing/repo r3
defaulting to local storage area
lan@lan's password:
Packing 204607 objects
Unpacking 204607 objects
Killed by signal 2.) done
real 4m0.874s
user 0m0.013s
sys 0m0.120s
I have killed it at ~ 20%. As I understand it does exactly what ssh git thru
ssh transport does: git-rev-list | git-pack | ssh | git-unpack or something
like this. So it is not faster.
next prev parent reply other threads:[~2005-10-25 11:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-25 7:49 How to clone faster via ssh ? Alexander Litvinov
2005-10-25 7:54 ` Alexander Litvinov
2005-10-25 9:04 ` Johannes Schindelin
2005-10-25 11:30 ` Alexander Litvinov [this message]
2005-10-25 17:17 ` Junio C Hamano
2005-10-26 2:46 ` Alexander Litvinov
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=200510251830.24550.lan@ac-sw.com \
--to=lan@ac-sw.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.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).