git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Potapov <dpotapov@gmail.com>
To: Michael Kerrisk <michael.kerrisk@googlemail.com>
Cc: 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 05:18:16 +0400	[thread overview]
Message-ID: <20080917011816.GL28210@dpotapov.dyndns.org> (raw)
In-Reply-To: <c49095e30809161640o21cb89b7x17a9ac1b5b18054f@mail.gmail.com>

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? If you use a version earlier than 1.5.6
than you can notice *considerable* speed up by upgrading to the latest
version of Git. Also, git-svn does not work well on Windows. Cygwin
version is slow due to fork(), and MSYS Git has some other issues with
Perl. So, if you want to convert a huge SVN repo, it is better to do on
Linux and using the latest version of Git. Perhaps, running on tmpfs may
speed up the process even more.

> 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?

Dmitry

  reply	other threads:[~2008-09-17  1:19 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 [this message]
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
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=20080917011816.GL28210@dpotapov.dyndns.org \
    --to=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 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).