From: Eric Wong <normalperson@yhbt.net>
To: Pazu <pazu@pazu.com.br>
Cc: git@vger.kernel.org
Subject: Re: git-svn: why fetching files is so slow
Date: Fri, 24 Nov 2006 12:33:20 -0800 [thread overview]
Message-ID: <20061124203320.GA21654@soma> (raw)
In-Reply-To: <loom.20061124T202153-512@post.gmane.org>
Pazu <pazu@pazu.com.br> wrote:
> Eric Wong <normalperson <at> yhbt.net> writes:
>
> > git-svn transfers full files, and not deltas. I'll hopefully have a
> > chance to look into improving the situation for slow links this weekend.
>
> Yes, but why would that make fetching the first revision slower? In this
> situation, both svn and git-svn would have to fetch full files. Maybe git-svn
> isn't using gzip compression or http pipelining?
Even for the initial transfer, the tree is bundled into one big delta
(at least over https).
--
next prev parent reply other threads:[~2006-11-24 20:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-24 13:36 git-svn: why fetching files is so slow Pazu
2006-11-24 17:10 ` Seth Falcon
2006-11-24 19:16 ` Eric Wong
2006-11-24 19:28 ` Pazu
2006-11-24 20:33 ` Eric Wong [this message]
2006-11-24 20:42 ` Junio C Hamano
2006-11-24 22:14 ` Eric Wong
2006-11-28 5:44 ` [PATCH 1/2] git-svn: enable delta transfers during fetches when using SVN:: libs Eric Wong
2006-11-28 10:29 ` [PATCH 1.1/2] git-svn: fix output reporting from the delta fetcher Eric Wong
2006-11-28 10:50 ` [PATCH 1.2/2 (fixed)] " Eric Wong
2006-11-28 12:45 ` Pazu
2006-11-28 15:32 ` Pazu
2006-11-28 16:07 ` Seth Falcon
2006-11-28 16:56 ` Pazu
2006-11-28 20:16 ` Eric Wong
2006-11-28 20:47 ` Pazu
2006-11-28 21:15 ` Eric Wong
2006-11-29 16:15 ` git-svn and empty directories in svn (was: [PATCH 1.2/2 (fixed)] git-svn: fix output reporting from the delta fetcher) Seth Falcon
2006-12-03 1:47 ` Eric Wong
2006-12-03 4:08 ` git-svn and empty directories in svn Steven Grimm
2006-12-04 21:33 ` Eric Wong
2006-11-28 5:46 ` [PATCH 2/2] git-svn: update tests for recent changes Eric Wong
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=20061124203320.GA21654@soma \
--to=normalperson@yhbt.net \
--cc=git@vger.kernel.org \
--cc=pazu@pazu.com.br \
/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.