将复杂的SVN存储库迁移到GIT

Question

I have a SVN Repository with more than 100 projects and I want to migrate to GIT now. This is how the SVN Repository looks like:

customer_1/prj_1 (trunk, branches, tags)
customer_1/prj_2 (trunk, branches, tags)
customer_1/prj_n (trunk, branches, tags)
...
customer_2/prj_1 (trunk, branches, tags)
customer_2/prj_2 (trunk, branches, tags)
customer_2/prj_n (trunk, branches, tags)
...
customer_n/prj_1 (trunk, branches, tags)
customer_n/prj_2 (trunk, branches, tags)
customer_n/prj_n (trunk, branches, tags)

Via SVN I can checkout:

1. The entire repository containing all customers and all projects
2. All projects of a single customer
3. A specific customer's project

I still need these three ways of access using GIT, especially branching and tagging single customer projects and not only the entire repository. So basically in SVN different customer projects have different stable releases being stored in the "tags" directory for each project. I need to differentiate between customer project releases in GIT as well.

I have converted the SVN Repository to a single GIT Repository (using svn-git), but as (I think) GIT does not allow to clone single folders like Subversion, it needs to be structured now by using submodules or subtrees.

Is it necessary to create a single GIT repository for every single customer project (which would take a lot of time) or what is the most common way to achieve what I was asking for?

Answer 1

If you need to tag individual customer projects, then you need one git repository per project. Tags (and branches) in git are global to their repository, there is no way to tag a subdirectory.

To do this using git-svn , run

git svn clone -s http://svn-repo/customer_1/prj_1 
git svn clone -s http://svn-repo/customer_1/prj_2

etc.

This may indeed take a while, but you'll probably have to live with that. You would of course script the calls to git-svn.

As to browsing the repositories:

If you have multiple git repos, you can just check them out as subfolders in one folder. If you want to browse them on the server, without cloning/checking out, you will need to install a git repository browser. There are many available - there's a list in the git wiki: Interfaces, frontends, and tools .