Do I follow our Lev version repository when the standard layout for git svn is param ( -s ) should currently use the standard layout though it was not the case for most of the history?
More info
In the first few years the main project folders were instead root in the trunk folder
/ - Project folders in the root - example After several years a migration branch was started and used for a few additional years / - folder in the project root - such as apps - components / branches - migration - for some time To be used as the main project work Took a long dwelling branch - eg.
has been in compliance with the current state standard layout for last one year
- / - No files, no folders (except trunk, branches, tags) in the root / branches - old migration - by changing the name of the migrating branch (moved) - like apps '- components' - some other branches (& lt; 5) '- Old root - Folder moved / tagged here' - About 150 tags for the release / trunk - e.g. To make it clear clearly, as we move forward, we do not plan to work with old migrations and old routes (low / checkout). It is only that we want history to reflect history as to how it was for the purpose of reading history and which files changed and why
In this situation, you can feed git-svn to several directories which cover trunk, branches and tags. All possibilities in history
I'll call it in two steps, git svn init and git svn fetch , a single GIT SVN clone To give a little more control
In your case it will be ...
git svn init - trunk = trunk / --trink = - branches = branches / - tag = tags / ... You can try the - trunk = branches / migrations , but sincerely I try to attempt to pretend to guit it, its historical branch (Possibly later merged into the new trunk), it was a trunk with everyone.
No comments:
Post a Comment