From: Andreas Ericsson <ae@op5.se>
To: Michael Kerrisk <michael.kerrisk@googlemail.com>
Cc: Dmitry Potapov <dpotapov@gmail.com>,
mtk.manpages@gmail.com, git@vger.kernel.org,
michael.kerrisk@gmail.com
Subject: Re: Getting correct tree layout when importing svn repo into git
Date: Wed, 17 Sep 2008 08:56:26 +0200 [thread overview]
Message-ID: <48D0AA1A.5060209@op5.se> (raw)
In-Reply-To: <c49095e30809162216m5c7885dbibbb022e65f43231c@mail.gmail.com>
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.
>> If you use a version earlier than 1.5.6
>> than you can notice *considerable* speed up by upgrading to the latest
>
> How much is "considerable"? My import is *still* running.
>
The greatest factor will usually be network round trip time, so if
this is a one-shot conversion, rsync the repository to somewhere
close and run the import over a local network. I've had some "fun"
trying to import sourceforge svn repositories that were large-ish
but not huge (same seat you're in, basically), but since I get up
to 800ms round trip time from sweden, conversion took forever.
>>
>>> Therefore, so far, I have not had a chance to run the command to
>>> completion to see if it gives the desired result. The greatly
>>> increased tun time also made me suspicious about whether the command
>>> was going to do the right thing. And, I end up with a lot of strange
>>> looking tags in the (as yet incompletely) imported tree:
>>>
>>> $ git branch -a
>>> tags/man-pages-2.00
>>> tags/man-pages-2.00@117
>>> tags/man-pages-2.01
>>> tags/man-pages-2.01@145
>>> tags/man-pages-2.02
>>> tags/man-pages-2.02@184
>>> tags/man-pages-2.03
>>> tags/man-pages-2.03@232
>>> tags/man-pages-2.04
>>> tags/man-pages-2.04@283
>>>
>>> What are the @nnn tags about?
>> I have never encounted them. Are you sure that you import into a clean
>> Git repo?
>
> Yes. It's a clean repo in a new directory.
>
I've seen such tags before. They were added by an automatic build bot
as a marker to say "hey, I just built this".
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
next prev parent reply other threads:[~2008-09-17 6: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 [this message]
2008-09-17 10:28 ` Michael Kerrisk
2008-09-17 10:42 ` Michael Gebetsroither
2008-09-17 10:56 ` Björn Steinbrink
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=48D0AA1A.5060209@op5.se \
--to=ae@op5.se \
--cc=dpotapov@gmail.com \
--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 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.