All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Subject: git-fetching from a big repository is slow
Date: Thu, 14 Dec 2006 13:40:36 +0000	[thread overview]
Message-ID: <200612141340.43925.andyparkins@gmail.com> (raw)

Hello,

I've got a big repository.  I've got two computers.  One has the repository 
up-to-date (164M after repack); one is behind (30M ish).

I used git-fetch to try and update; and the sync took HOURS.  I zipped 
the .git directory and transferred that and it took about 15 minutes to 
transfer.

Am I doing something wrong?  The git-fetch was done with a git+ssh:// URL.  
The zip transfer with scp (so ssh shouldn't be a factor).



Andy
-- 
Dr Andy Parkins, M Eng (hons), MIEE

             reply	other threads:[~2006-12-14 13:41 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-14 13:40 Andy Parkins [this message]
2006-12-14 13:53 ` git-fetching from a big repository is slow Andreas Ericsson
2006-12-14 14:14   ` Johannes Schindelin
2006-12-14 15:06     ` Andreas Ericsson
2006-12-14 19:05       ` Geert Bosch
2006-12-14 19:46         ` Shawn Pearce
2006-12-14 22:12           ` Horst H. von Brand
2006-12-14 22:38             ` Shawn Pearce
2006-12-15 21:49               ` Pazu
2006-12-16 13:32                 ` Robin Rosenberg
2006-12-14 23:01           ` Geert Bosch
2006-12-14 23:15           ` Johannes Schindelin
2006-12-14 23:29             ` Shawn Pearce
2006-12-15  0:07               ` Johannes Schindelin
2006-12-15  0:42                 ` Shawn Pearce
2006-12-15  2:26             ` Nicolas Pitre
2006-12-14 22:28         ` Andreas Ericsson
2006-12-14 15:18   ` Andy Parkins
2006-12-14 15:45     ` Han-Wen Nienhuys
2006-12-14 16:20       ` Andy Parkins
2006-12-14 16:34         ` Johannes Schindelin
2006-12-14 20:41           ` Junio C Hamano
2006-12-14 23:26             ` Johannes Schindelin
2006-12-15  0:38               ` Junio C Hamano
2006-12-14 18:14   ` Nicolas Pitre

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=200612141340.43925.andyparkins@gmail.com \
    --to=andyparkins@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.