This whole scenario is not a 1:1 copy-and-it-works suggestion but more of a generic model. Tags are just "symlinks" to revision so both scenarios use the same principle.
more complicated to setup & understand (whole team has to).tagging overhead scales and remains constant on main tag-day.documentation is a bit easier via svn history and revision graph.Once you have created the directory structure, you can then move the pre-existing project files into the trunk folder. Step 3: Create project folders within /myrepository. Now clone the Subversion repository: git svn clone -s -A users.txt svn://hostname/path destdir-tmp cd destdir-tmp git. Here are the steps for creating your subversion repository. For example, users.txt: user1 First Last Name user2 First Last Name. Create a users file so you can correctly map SVN commit usernames to Git users. If that is not the case tagging and using fixed taggs for release-integration can be verry smooth. Importing Subversion Repositories with Branches and Tags to Git. Problem here is that your application layout indicates that project1 and 2 reside inside your main application "/". svn copy You can use a revision number too.They can decide to use the revision number or simply tag HEAD when they are ready: git init -bare /new-bare.git cd /new-bare.git git symbolic-ref HEAD refs. First, create a bare repository and make its default branch match svn’s trunk branch name. Push repository to a bare git repository. Whoever checks out your main app will now get the latest versions of your projects when they were ready for release.ĭevelopment teams for the projects do these steps whenever a new release is ready. gitignore git commit -m Convert svn:ignore properties to. create a file in an editor and call it "externals".overhead scales lineary with number of projects.