Re: Getting correct tree layout when importing svn repo into git
- From
Björn Steinbrink <b.steinbrink@gmx.de>
- Date
- Sep 17, 2008, 10:56 UTC
- Message-ID
- <20080917105620.GA13144@atjola.homenet>
- In-Reply-To
- <cfd18e0f0809170328pb039331m1c4dc42fd398a4d@mail.gmail.com>
On 2008.09.17 03:28:46 -0700, Michael Kerrisk wrote:
Show 27 quoted lines
> 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.
Show 13 quoted lines
> $ 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