From: Martin Langhoff <martin.langhoff@gmail.com>
To: Keith Packard <keithp@keithp.com>
Cc: Andreas Ericsson <ae@op5.se>, Linus Torvalds <torvalds@osdl.org>,
Junio C Hamano <junkio@cox.net>,
Git Mailing List <git@vger.kernel.org>,
Petr Baudis <pasky@suse.cz>
Subject: Re: Make "git clone" less of a deathly quiet experience
Date: Mon, 13 Feb 2006 15:06:42 +1300 [thread overview]
Message-ID: <46a038f90602121806jfcaac41tb98b8b4cd4c07c23@mail.gmail.com> (raw)
In-Reply-To: <1139717510.4183.34.camel@evo.keithp.com>
On 2/12/06, Keith Packard <keithp@keithp.com> wrote:
> On Sun, 2006-02-12 at 04:43 +0100, Andreas Ericsson wrote:
>
> > A weird oddity; Cloning is faster over rsync, day-to-day pulling is not.
>
> Precisely. If the protocol could deliver existing packs instead of
> unpacking and repacking them, then git would be as fast as rsync and I
> wouldn't have to worry about supporting two protocols.
+1... there should be an easy-to-compute threshold trigger to say --
hey, let's quit being smart and send this client the packs we got and
get it over with. Or perhaps a client flag so large projects can
recommend that uses do their initial clone with --gimme-all-packs?
My workaround for large repos is to clone over http, and s/http:/git:/
on the origin file once it's done ;-)
martin
next prev parent reply other threads:[~2006-02-13 2:06 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-11 4:31 Make "git clone" less of a deathly quiet experience Linus Torvalds
2006-02-11 4:37 ` Linus Torvalds
2006-02-11 5:50 ` Junio C Hamano
2006-02-11 17:39 ` Linus Torvalds
2006-02-11 5:48 ` Junio C Hamano
2006-02-11 7:35 ` Craig Schlenter
2006-02-11 8:44 ` Radoslaw Szkodzinski
2006-02-11 13:05 ` Petr Baudis
2006-02-11 13:15 ` Radoslaw Szkodzinski
2006-02-11 13:33 ` Petr Baudis
2006-02-11 13:41 ` Petr Baudis
2006-02-11 17:24 ` Alex Riesen
2006-02-11 17:45 ` Linus Torvalds
2006-02-11 19:10 ` Keith Packard
2006-02-12 3:43 ` Andreas Ericsson
2006-02-12 4:11 ` Keith Packard
2006-02-12 11:02 ` Andreas Ericsson
2006-02-12 21:04 ` Keith Packard
2006-02-16 6:56 ` Eric W. Biederman
2006-02-16 7:33 ` Junio C Hamano
2006-02-13 2:06 ` Martin Langhoff [this message]
2006-02-13 3:36 ` Junio C Hamano
2006-02-11 18:39 ` Alex Riesen
2006-02-11 19:04 ` Linus Torvalds
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=46a038f90602121806jfcaac41tb98b8b4cd4c07c23@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=keithp@keithp.com \
--cc=pasky@suse.cz \
--cc=torvalds@osdl.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).