From: "Björn Steinbrink" <B.Steinbrink@gmx.de>
To: mtk.manpages@gmail.com
Cc: Andreas Ericsson <ae@op5.se>,
Michael Kerrisk <michael.kerrisk@googlemail.com>,
Dmitry Potapov <dpotapov@gmail.com>,
git@vger.kernel.org, michael.kerrisk@gmail.com,
Michael J Gruber <git@drmicha.warpmail.net>
Subject: Re: Getting correct tree layout when importing svn repo into git
Date: Wed, 17 Sep 2008 12:56:20 +0200 [thread overview]
Message-ID: <20080917105620.GA13144@atjola.homenet> (raw)
In-Reply-To: <cfd18e0f0809170328pb039331m1c4dc42fd398a4d@mail.gmail.com>
On 2008.09.17 03:28:46 -0700, Michael Kerrisk wrote:
> Hi Andreas,
>
> On Tue, Sep 16, 2008 at 11:56 PM, Andreas Ericsson <ae@op5.se> wrote:
> > Michael Kerrisk wrote:
> >>
> >> Hi Dimitry,
> >>
> >> On Tue, Sep 16, 2008 at 6:18 PM, Dmitry Potapov <dpotapov@gmail.com>
> >> wrote:
> >>>
> >>> On Wed, Sep 17, 2008 at 01:40:36AM +0200, Michael Kerrisk wrote:
> >>>>
> >>>> $ git svn init file:///home/mtk/man-pages-rep/ -t tags -T trunk -b
> >>>> branches
> >>>>
> >>>> takes about half an hour to run, the other command (which I already
> >>>> started yesterday) seems to be taking (far) more than a day!
> >>>
> >>> What version of Git do you use?
> >>
> >> 1.5.4.5, on Linux.
> >>
> >
> > An upgrade would do you good.
>
> But, is it going to make this much difference to the run time? By
> now, the import using
It should.
> $ git svn init file:///home/mtk/man-pages-rep/ -t tags -T
> trunk/man-pages -b branches
>
> has been running for over 2 days (and I still don't know if it will
> give the layout I want), and seems to be slowing down exponentially as
> it gets further along in the import process, so at this rate it looks
> like it would take several more days to complete, whereas
>
> $ git svn init file:///home/mtk/man-pages-rep/ -t tags -T trunk -b branches
>
> which doesn't give the layout I want, takes less than an hour. We're
> talking about a factor of at least 100 x in the speed difference for
> the two imports.
I guess your old import doesn't see any relations between the trunk and
the tags/branches, right? Then the huge increase in runtime would be, at
least in part, explained by git-svn searching for ancestry. That you see
those tags/1.2.3@123 things also means that the 1.2.3 tags got deleted
and recreated, or at least git-svn thinks so. Maybe the ancestry
detection goes nuts, hard to tell.
Is that svn repo available anywhere?
Björn
next prev parent reply other threads:[~2008-09-17 10:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-16 22:05 Getting correct tree layout when importing svn repo into git Michael Kerrisk
2008-09-16 23:20 ` Dmitry Potapov
2008-09-16 23:40 ` Michael Kerrisk
2008-09-17 1:18 ` Dmitry Potapov
2008-09-17 5:16 ` Michael Kerrisk
2008-09-17 6:56 ` Andreas Ericsson
2008-09-17 10:28 ` Michael Kerrisk
2008-09-17 10:42 ` Michael Gebetsroither
2008-09-17 10:56 ` Björn Steinbrink [this message]
2008-09-17 12:53 ` Michael Kerrisk
2008-09-17 8:25 ` Michael J Gruber
2008-09-17 10:38 ` Michael Kerrisk
2008-09-17 11:05 ` Björn Steinbrink
2008-09-17 12:57 ` Michael Kerrisk
2008-09-17 11:14 ` Michael J Gruber
2008-09-17 13:00 ` Michael Kerrisk
2008-09-17 13:04 ` Michael J Gruber
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=20080917105620.GA13144@atjola.homenet \
--to=b.steinbrink@gmx.de \
--cc=ae@op5.se \
--cc=dpotapov@gmail.com \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=michael.kerrisk@gmail.com \
--cc=michael.kerrisk@googlemail.com \
--cc=mtk.manpages@gmail.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).