evil twin

[kernelk]

I am new to plastic. I did:

cm co .

echo 1 > foo.txt

cm add foo.txt

cm ci . foo.txt

cm co foo.txt

echo 2 > foo.txt

cm ci foo.txt

cm hst foo.txt

cm co .

cm rm foo.txt

cm ci .

cm co .

echo 1 > foo.txt

cm add foo.txt

cm ci . foo.txt

cm hst foo.txt

In ClearCase this is called an eviltwin; Two different elements that resolve to the same path. We created CC triggers to prevent this behavior and link in a version of the original element and create a new version of it.

How do you prevent this in plastic?

[kernelk]

Maybe my example is not clear, so let me describe it differently.

Imagine that 2 users working in the same repository, are on separate branches, and each add a new file ({workspace}/foo.txt). The 2 new files are not related in the tree because they are unique entries in the repository.

What would be the best way to automatically link files that resolve to the same path but are not visible either due to being removed from the parent directory or existing on other branches?