Hello all, I am in process of re-organizing our current repository and in process, few of the modules will be re-parented. For example current top level module "foo" may become second level module under "bar" as "bar/foo". This is good so far, but it also is about to break our current capabilities. Let me explain the scenario by example.
Say, currently, we have "foo" and "submodule" as as below: foo/submodule we have certain automated capability, which depends on this layout and performs check out as below: cvs co -d submodule foo/submodule Re-parenting "foo" to "bar" bar/foo/submodule certainly breaks our current capability. I have tried fixing it by manipulate modules file by defining alias such as foo -a bar/foo but this does not solve problem, when I check out the submodule with following command: cvs co -d submodule foo/submodule It checks out foo, not submodule. Defining regular module as below Foo bar/foo also did not help. Is there a way to fix this? I appreciate your help. h s
