git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Asuka <c.bauers@gmx.de>
To: git@vger.kernel.org
Subject: How to migrate a complex directory structure from SVN to GIT?
Date: Tue, 17 Jan 2012 11:33:57 -0800 (PST)	[thread overview]
Message-ID: <1326828837924-7197567.post@n2.nabble.com> (raw)

Hi there,

I would like to migrate my svn repository to git. The structure looks like
the following:

svn
   |_Project1
         |_subproject1
               |_branches
                      |_branch1
                      |_branch2
               |_trunk
               |_tags
                      |_tagv1
   |_Non-JavaProject
         |_subproject
   |_Project2
          |_AnotherSubproject
               |_SubSubproject
          |_Subproject2
               |_branches
               |_tags
          |_Subproject3
               |_trunk
          |_Subproject4
               |_Subsubproject
                       |_branches
                       |_tags
                       |_trunk

I would like to migrate all branches and tags .. but unfortunately sometimes
I have just a trunk directory and no branches or tags directory. Sometimes
the branches are in a subdirectory, sometimes in a subsubdirectory. So how
can migrate my svn in an efficient way?

Thanks in advance
Best wishes

--
View this message in context: http://git.661346.n2.nabble.com/How-to-migrate-a-complex-directory-structure-from-SVN-to-GIT-tp7197567p7197567.html
Sent from the git mailing list archive at Nabble.com.

             reply	other threads:[~2012-01-17 19:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-17 19:33 Asuka [this message]
2012-01-18 10:43 ` How to migrate a complex directory structure from SVN to GIT? Michael Haggerty
2012-01-18 18:47 ` Jehan Bing
2012-01-27  4:46   ` David Barr

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=1326828837924-7197567.post@n2.nabble.com \
    --to=c.bauers@gmx.de \
    --cc=git@vger.kernel.org \
    /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).