From: John Koleszar <john.koleszar@on2.com>
To: Yann Dirson <ydirson@altern.org>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: git-svn: importing internal externals
Date: Fri, 29 May 2009 17:05:19 -0400 [thread overview]
Message-ID: <1243631119.6276.46.camel@cp-jk-linux.corp.on2.com> (raw)
In-Reply-To: <20090528112542.GA24403@nan92-1-81-57-214-146.fbx.proxad.net>
On Thu, 2009-05-28 at 07:25 -0400, Yann Dirson wrote:
> On Wed, May 27, 2009 at 12:51:29PM -0400, John Koleszar wrote:
> > Hi,
> >
> > I'm working on a one-off import of an SVN repo that makes use of
> > "internal" svn:externals; i.e. all URLs refer to different spots in the
> > same repo, potentially with peg revisions. The SVN repo holds a number
> > of projects, and my plan is to import them into individual git repos,
> > incorporating the history from any svn:external linked sub-projects.
>
[...]
> It can be a good idea to share your script nevertheless :)
>
I hacked on this some more and got something pretty usable (for me). It
operates on a git-svn clone of the whole repository, propagates commits
to different paths if referenced by an external, rearranges the tree to
isolate each svn branch on its own head, reparents the branches to their
proper branch points, and converts any tags branches to real git tags.
Don't know what the netequitte is on this list regarding attachments for
this sort of thing, so I posted it here:
http://github.com/jkoleszar/git-svn-internal-externals/tree/master
It's not as fast as I'd like, but it's workable, at least for small
repositories. Bottleneck seems to be git-update-index (100s of ms/call)
but I haven't looked into it too much. I'm sure I could be smarter in
some of my pipelines too. Some numbers (2246 revisions, ~15k files,
Core2 6600 @ 2.4GHz, tmpfs):
git-svn fetch:
197.03user 174.63system 22:36.59elapsed 27%CPU (0avgtext+0avgdata
0maxresident)k 0inputs+0outputs (0major+35448577minor)pagefaults 0swaps
propagating externals:
1381.29user 744.42system 34:28.67elapsed 102%CPU (0avgtext+0avgdata
0maxresident)k 0inputs+0outputs (2major+305234667minor)pagefaults 0swaps
rearranging heads:
46.13user 64.23system 1:52.42elapsed 98%CPU (0avgtext+0avgdata
0maxresident)k 0inputs+0outputs (4major+28752709minor)pagefaults 0swaps
reparenting branches:
151.52user 263.50system 6:19.54elapsed 109%CPU (0avgtext+0avgdata
0maxresident)k 0inputs+0outputs (2major+135830914minor)pagefaults 0swaps
Hope this is useful for someone!
John
next prev parent reply other threads:[~2009-05-29 21:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-27 16:51 git-svn: importing internal externals John Koleszar
2009-05-28 11:25 ` Yann Dirson
2009-05-29 21:05 ` John Koleszar [this message]
2009-06-10 21:58 ` Yann Dirson
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1243631119.6276.46.camel@cp-jk-linux.corp.on2.com \
--to=john.koleszar@on2.com \
--cc=git@vger.kernel.org \
--cc=ydirson@altern.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).