This content has been marked as final. Show 5 replies
This statement may apply only to RoboSource Control. I use Subversion, and if I were to rename a project, Subversion just sees all the renamed files as new files that are not under version control.
At that point, I just have to pull the old files back down from the repository (because they're not there in Windows Explorer anymore) and set them to be deleted. Then I add all the renamed files. When I commit the whole bunch, the old ones are deleted from the repository and the renamed ones are committed.
I can't give any assurances for other version control software.
Just a note--this applies also if I change the file name for any topics (which I do in RH rather than Windows Explorer of course). I avoid changing file names but have still had to do it from time to time. Subversion handles it fine.
What I've done is remove the project from source control, rename it, and then add it to a new database. That's not elegant, but it worked.
Thanks, I had considered this approach. I will give it a try.
When you remove a project from RoboSource Control, doesn't that erase the history?