git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Kerrisk" <michael.kerrisk@googlemail.com>
To: "Dmitry Potapov" <dpotapov@gmail.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 01:40:36 +0200	[thread overview]
Message-ID: <c49095e30809161640o21cb89b7x17a9ac1b5b18054f@mail.gmail.com> (raw)
In-Reply-To: <37fcd2780809161620v38d9ade0sc1a2715f79501c6f@mail.gmail.com>

Hello Dmitry,

On Wed, Sep 17, 2008 at 1:20 AM, Dmitry Potapov <dpotapov@gmail.com> wrote:
> On Wed, Sep 17, 2008 at 2:05 AM, Michael Kerrisk
> <mtk.manpages@googlemail.com> wrote:
>>
>> I'm currently trying to import an svn repository, along with its tags,
>> into git, and everything seems okay except that after the import I
>> expect to have the following structure to my checked out repository:
>>
>>    [root-dir]
>>        .git
>>        <checked-out-files>
>>
>> But instead I end up with
>>
>>    [root-dir]
>>        .git
>>        man-pages               <-- name of my svn project
>>            <checked-out-files>
>>
>> I've tried out a few different command-line flag settings but so far I
>> haven't managed to get the desired layout.  I guess that I'm missing
>> something trivial, but I haven't worked out what it is so far.
>>
>> The commands I'm using to do the import are:
>>
>> $ git svn init file:///home/mtk/man-pages-rep/ -t tags -T trunk -b branches
>
> Probably, you want to run:
>
> $ git svn init file:///home/mtk/man-pages-rep/ -t tags -T
> trunk/man-pages -b branches

I had wondered about this.  And I haven't yet had a chance to verify
the result.  The reason is that whereas the command:

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

By tomorrow, probably the command will complete and I can see whether
it produces the desired result.  But why does it take so much longer
to run this version of the command?

Cheers,

Michael

  reply	other threads:[~2008-09-16 23:41 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 [this message]
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
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=c49095e30809161640o21cb89b7x17a9ac1b5b18054f@mail.gmail.com \
    --to=michael.kerrisk@googlemail.com \
    --cc=dpotapov@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=michael.kerrisk@gmail.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).