Michael Kerrisk wrote:
Hi Dimitry,
On Tue, Sep 16, 2008 at 6:18 PM, Dmitry Potapov <dpotapov@xxxxxxxxx> 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@xxxxxx
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html