git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pascal Obry <pascal@obry.net>
To: David Michael Barr <david.barr@cordelta.com>
Cc: git@vger.kernel.org
Subject: Re: Subversion integration with git
Date: Thu, 25 Mar 2010 19:23:44 +0100	[thread overview]
Message-ID: <4BABAA30.3080806@obry.net> (raw)
In-Reply-To: <3311ED3F-77BC-4F66-80D5-AA9E21ACF0E2@cordelta.com>

David,

> My project is still in the preview phase but has enough to import 
> commit-tree structure bar symlinks and executable flags. It imports 
> my 22000+ commit 2.8GB dump in 4 minutes. It is currently 840 
> non-comment lines of C. I aim to produce output that git-svn can
> take over from.

Impressive numbers! I've converted many projects using git-svn and yes
it is slow. Just curious, does it handles branches? Can it handles not
standard layout (trunk/branch/tags)? When you have a git-svn compatible
output I would be willing to test it on a project.

Pascal.

-- 

--|------------------------------------------------------
--| Pascal Obry                           Team-Ada Member
--| 45, rue Gabriel Peri - 78114 Magny Les Hameaux FRANCE
--|------------------------------------------------------
--|    http://www.obry.net  -  http://v2p.fr.eu.org
--| "The best way to travel is by means of imagination"
--|
--| gpg --keyserver keys.gnupg.net --recv-key F949BD3B

  parent reply	other threads:[~2010-03-25 18:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-25 14:17 Subversion integration with git David Michael Barr
2010-03-25 14:31 ` Erik Faye-Lund
     [not found]   ` <E560EF9A-AF07-4316-9047-6D1A1802F743@cordelta.com>
2010-03-25 17:52     ` Ramkumar Ramachandra
2010-03-25 23:50       ` David Michael Barr
2010-03-30 14:05       ` David Michael Barr
2010-03-30 14:29         ` Ramkumar Ramachandra
2010-03-25 18:23 ` Pascal Obry [this message]
2010-03-28 12:03   ` David Michael Barr

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=4BABAA30.3080806@obry.net \
    --to=pascal@obry.net \
    --cc=david.barr@cordelta.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 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).