From: Jeff King <peff@peff.net>
To: Victor Leschuk <vleschuk@accesssoftek.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: git-svn: Why not use git-fast-import?
Date: Tue, 22 Sep 2015 11:59:29 -0400 [thread overview]
Message-ID: <20150922155928.GA16221@sigill.intra.peff.net> (raw)
In-Reply-To: <6AE1604EE3EC5F4296C096518C6B77EE5D0FDAB9D7@mail.accesssoftek.com>
On Tue, Sep 22, 2015 at 02:12:59AM -0700, Victor Leschuk wrote:
> I've been playing with git-svn for some time already and as it seems
> to me there are two most important problems which make it hard to use
> in production for large repositories. Very low speed and large memory
> footprint of synchronization with SVN repos (I am talking about clone
> and fetch operations mostly). I was wondering why the git-fast-import
> is not used for these purposes? Are there any serious limitations
> which make it impossible?
The main reason is that git-svn predates the invention of fast-import.
There was an attempt later to make a more "modern" svn interface:
- it would provide a git-remote-helper interface (so you could use
normal clone, fetch, and push with an "svn::" URL rather than a
separate git-svn).
- it would use fast-import for moving data into git
but it was never finished. I don't recall the specific problems offhand.
You can see the remnants in the vcs-svn directory of git, or you might
find discussions by searching the list archive.
-Peff
prev parent reply other threads:[~2015-09-22 15:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-22 9:12 git-svn: Why not use git-fast-import? Victor Leschuk
2015-09-22 15:59 ` Jeff King [this message]
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=20150922155928.GA16221@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=vleschuk@accesssoftek.com \
/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).