All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Clatworthy <ian.clatworthy@internode.on.net>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Bazaar <bazaar@lists.canonical.com>, git@vger.kernel.org
Subject: Re: [Fwd: [ANNOUNCE] bzr-fastimport plugin, yet another Bazaar import option]
Date: Fri, 22 Feb 2008 17:47:40 +1000	[thread overview]
Message-ID: <47BE7E1C.4040303@internode.on.net> (raw)
In-Reply-To: <20080222073228.GF8410@spearce.org>

Shawn O. Pearce wrote:

> If we are heading in the direction of making this a common stream
> format I'd like to try and work it out such that any additional
> extensions aren't VCS specific, at least as much as we can avoid it.
> That way exports from a source into this format can be loaded into
> any VCS that recognizes it, and have little or no loss.  So yes,
> I am interested in trying to work with you and anyone else who wants
> to extend the format further.

Excellent. That sounds the right way to go. I'll contact you if and when
I want to add stuff.

> Heh.  OOo is _huge_.  I think the best import into Git thus far is
> taking up about 1.5G of disk space once fully repacked.  I don't
> recall how they did the import, but coming from SVN I think they
> used git-svn, which is not based on git-fast-import.
> 
> What frontend are you using to go from SVN -> fast-import?

The pack file in the Git clone I have is 2.4G. I thought that was large
but it's quite small compared to the 82G svn dump that creates a 55G svn
repo!

I'm using svn-fast-export.c currently. I'd rather enhance the Python one
but my Subversion binding knowledge is slim and there's a bug wrt "too
many open files" that causes it to crash almost immediately on the OOo
repo. It's not obvious to me how to fix that unfortunately. It worked
fine for Wordpress OTOH.

The svn-all-fast-export tool sounds interesting but is completely
undocumented to my knowledge.

Ian C.

  reply	other threads:[~2008-02-22  7:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <47BE167A.4060005@internode.on.net>
2008-02-22  7:32 ` [Fwd: [ANNOUNCE] bzr-fastimport plugin, yet another Bazaar import option] Shawn O. Pearce
2008-02-22  7:47   ` Ian Clatworthy [this message]
2008-02-22 10:36     ` Johannes Schindelin
2008-02-22 10:33   ` Johannes Schindelin
2008-02-22 11:37   ` Pierre Habouzit
2008-02-22 11:47     ` cvs2svn, was " Johannes Schindelin
2008-02-22 13:14     ` Michael Haggerty
2008-02-22 14:44     ` Aidan Van Dyk
2008-02-22 18:20       ` Pierre Habouzit
2008-02-22 19:25         ` Aidan Van Dyk

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=47BE7E1C.4040303@internode.on.net \
    --to=ian.clatworthy@internode.on.net \
    --cc=bazaar@lists.canonical.com \
    --cc=git@vger.kernel.org \
    --cc=spearce@spearce.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.