- Where Developers Learn, Share, & Build Careers
There is a very large heritage CVS repo (66 GB) in our decade and is increasing. Now we have some sub-contract companies, who have to work on some modules and branches.
We have to make some branches for them and send them to the branches. Apart from this, we need to merge our changes in our main branches from time to time.
We are concerned:
-
We can not repay them completely, mostly
-
We need to send them some history information, not the "Head" code version.
-
We are still doing some development work, so we need to send changes from time to time.
Is GIT and Mercurial a good option for displacement with CIS? GIT / MERSUREAL can satisfy our needs?
EDIT: I think we need a centralized revision control with multi-site facility, with the ability to make off-site repos based on the part of the Central Repo. And can be easily merged between sites.
With GIT, you can use the command "cut" to subdirectories you Subcontractors can, and then easily add their changes to their mainline. You can also update them from time to time if you need it, the
git subtree command was an add-on, but it rolled into the official code distribution code in the contrib I went.
It is possible that you limit the amount of history involved in a repository given to an external user.
I hope to be your biggest concern, however, with such a large initial repo will move to a DVC. Git will hesitate in your repo, when you do not have the possibility of getting 66 GB, but it is still unbearable (probably on the order of 10 GB, depending on what you have stored there). If you do not consider that problem, go for it.
I limited my responses to Git because I'm more familiar with Grit.
Comments
Post a Comment