- Ask a related questionWhat is a related question?A related question is a question created from another question. When the related question is created, it will be automatically linked to the original question.
I am using CCS v5.5. As we all know, often there is a need to branch (fork?) software in a Source Control (Revision Control) system for maintenance, variants, and starting point for derivative work. This creates an alternate project of the same name. We do this a fair amount. In some cases, this branched effort gets merged back to the root view; Sometimes it does not.
However, when I try to import this duplicate, but different directory, project into CCS, it will list it but it will NOT let me CHECK it (check box) for import. I suppose I can remedy this by creating a new workspace. Currently I have one workspace: C:\ti\wkspace. I really don't like the idea of having a bunch of workspaces and trying to remember which branch view belongs to which workspace. If that is the case, I would rather have the older CCS 3.3 model where you just go to the project file and open it, taking workspaces out of the picture altogether.
As branching projects is a common occurrence, is there a way for CCS to handle duplicate project names that are in separate folder sets? It could present an alias to the user by appending a number or path segment, etc.
Regards,
Jim
