RE: [cciug] A file element has lost its link with other branches.

From: Chris.Moore@infineon.com
Date: Mon Sep 25 2000 - 11:09:30 EDT


I came across this a while ago. It's a well known condition, known as "evil twins". There are lots of references to this 'problem' on the CCIUG archives.

Basically, you have two different elements with the same name. Most people on this list seem to have a trigger or 2 in place to detect and prevent the creation of evil twins.

I didn't find a good general way to merge the two elements into a single element, but for your case it doesn't sound like it would be too hard, since there is no overlap between the two. Unfortunately you can't use 'ct merge' to do the job, since ClearCase can only merge between versions of a single element.

I've attached a reply that I received on this list about a month ago on the subject.

Chris.

-----Original Message-----
From: Selvakumar, Sudharsan [mailto:sudharsan.selvakumar@verizon.com
Sent: 25 September 2000 15:48
To: cciug@rational.com
Subject: [cciug] A file element has lost its link with other branches.

HI CCIUG Friends,

                           I have a file element say test.vbp. And it exists
in four branches. when I look at the version tree of that file element from
the main branch I can see that it exists in all the four branches and I can
see version 0 of that file in the bufix branch(one of the 4 branches) .
But when when I look at the version tree from the bugfix branch view of the
same file element I can see that it has more than 10 versions in bugfix
branch, and it doesnt have any versions in any of the other 3 branches.
when I look at the history for test.vbp from bugfix branch I can see that a
new version has been created. But the file name (test.vbp) is same in all
the branches.

                          So i think it has lost the link with other
branches. can anybody helpme, to link it back!!!

Thanks in advance

Sudharsan

 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -


attached mail follows:


You have discovered the "evil twin" problem. The solution is to write a
mkelem _preop_ trigger that will create a link instead of making the
element, then return a non-zero exit status, bypassing the mkelem step
altogether. If a view private file exists, then you may need to move it
yourself, create the link, check out the element and move it back,
emulating mkelem's operations somewhat.

--
cg

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -



This archive was generated by hypermail 2b29 : Sun May 06 2001 - 00:26:48 EDT