public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor•com>
To: Petr Baudis <pasky@ucw•cz>
Cc: Sean <seanlkml@sympatico•ca>, git@vger•kernel.org
Subject: Re: Local clone/fetch with cogito is glacial
Date: Mon, 22 May 2006 15:23:44 -0700	[thread overview]
Message-ID: <447239F0.9030705@zytor.com> (raw)
In-Reply-To: <20060522220206.GA10488@pasky.or.cz>

Petr Baudis wrote:
> 
> What about incremental fetches using git-fetch? From a quick scan of the
> git-fetch automagic tags following code, it seems to be even
> significantly more expensive than Cogito's (in terms of number of
> forks).
> 

Well, I haven't used git-fetch, so I can't comment on that one.

> git-clone has an advantage here since it clones _everything_ while
> Cogito fetches only stuff related to the branch you are cloning, and
> verifying if what it fetches is sensible for you unfortunately takes a
> lot of time. :/ I guess there is no way to verify presence of multiple
> objects at once and there is also no way to order local fetch of
> multiple objects at once.

Note that non-local cg-clones are at least an order of magnitude faster, even when the 
nonlocal is just git+ssh:.  One could presumably do the same thing over a pipe.

	-hpa

  reply	other threads:[~2006-05-22 22:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-21 23:47 Local clone/fetch with cogito is glacial H. Peter Anvin
     [not found] ` <20060521212026.22f36e03.seanlkml@sympatico.ca>
2006-05-22  1:20   ` Sean
2006-05-22 21:18     ` H. Peter Anvin
2006-05-22 22:02       ` Petr Baudis
2006-05-22 22:23         ` H. Peter Anvin [this message]
2006-05-22 22:50           ` Petr Baudis
2006-05-22 23:03             ` H. Peter Anvin
2006-05-22 23:08               ` Petr Baudis
2006-05-22 23:18             ` Linus Torvalds
2006-05-22 23:24               ` Petr Baudis
2006-05-22  1:40 ` 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=447239F0.9030705@zytor.com \
    --to=hpa@zytor$(echo .)com \
    --cc=git@vger$(echo .)kernel.org \
    --cc=pasky@ucw$(echo .)cz \
    --cc=seanlkml@sympatico$(echo .)ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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