Forums : Technical Issue Help
Dear Open Hub Users,
We’re excited to announce that we will be moving the Open Hub Forum to
https://community.blackduck.com/s/black-duck-open-hub.
Beginning immediately, users can head over,
register,
get technical help and discuss issue pertinent to the Open Hub. Registered users can also subscribe to Open Hub announcements here.
On May 1, 2020, we will be freezing https://www.openhub.net/forums and users will not be able to create new discussions. If you have any questions and concerns, please email us at
[email protected]
enlistments
Hi,
If a project switches its scm, should it delete the previous source code enlistments? Or will this mess up the history of the project?
Specifically I am talking about Wings 3D. We just switched from svn to git, and there is even an enlistment to the cvs tree with which the project started.
I believe the history from the svn was carried over to Git using a conversion tool, but the cvs tree is the only record of the first years of the Wings 3D project.
I just added the new Git repository.
Please advise as to deleting the svn enlistment.
If it is no trouble to leave them all, then that's fine with me too :)
Regards,
Richard
Hi optigon,
The main goal should be to capture all of the commits, to capture them each once.
If the Subversion history was migrated into Git, then I recommend removing the Subversion enlistment. This will avoid double-counting those commits.
If the CVS history is unavailable anywhere else, I would keep the CVS.
