Is there a version tree in RTC?

Hi
I did a import from base CC to RTC and want to verify a couple of things.
"trigger" is the root folder in BaseCC vob in base CC, which has three version in main and 1 in a bugfix branch.
I want to see if the imported has the same structure. How can I see that? I find noway to display the history of this root folder in RTC.
http://i55.tinypic.com/2ahyuep.png
I did a import from base CC to RTC and want to verify a couple of things.
"trigger" is the root folder in BaseCC vob in base CC, which has three version in main and 1 in a bugfix branch.
I want to see if the imported has the same structure. How can I see that? I find noway to display the history of this root folder in RTC.
3 answers

RTC does not yet support a version tree for directories.
But even if it did, you wouldn't see the same structure as you would see
in ClearCase, because in RTC, a file/directory version knows its parent
(and knows the name of its parent), while in ClearCase, it is the
directory version that knows about its children.
So in RTC, you only get a new version of a directory if you move or
rename that directory, whereas if you move/rename a member of that
directory, you'd get a new version of that member.
Cheers,
Geoff
On 10/25/2011 10:53 AM, hujirong wrote:
But even if it did, you wouldn't see the same structure as you would see
in ClearCase, because in RTC, a file/directory version knows its parent
(and knows the name of its parent), while in ClearCase, it is the
directory version that knows about its children.
So in RTC, you only get a new version of a directory if you move or
rename that directory, whereas if you move/rename a member of that
directory, you'd get a new version of that member.
Cheers,
Geoff
On 10/25/2011 10:53 AM, hujirong wrote:
Hi
I did a import from base CC to RTC and want to verify a couple of
things.
"trigger" is the root folder in BaseCC vob in base CC, which
has three version in main and 1 in a bugfix branch.
I want to see if the imported has the same structure. How can I see
that? I find noway to display the history of this root folder in
RTC.
http://i55.tinypic.com/2ahyuep.png

RTC does not yet support a version tree for directories.
But even if it did, you wouldn't see the same structure as you would see
in ClearCase, because in RTC, a file/directory version knows its parent
(and knows the name of its parent), while in ClearCase, it is the
directory version that knows about its children.
So in RTC, you only get a new version of a directory if you move or
rename that directory, whereas if you move/rename a member of that
directory, you'd get a new version of that member.
Cheers,
Geoff
Thanks, I guess this change is to resolve the notorious activity dependency issue in CC.
Jirong

Actually, the activity dependency issue in UCM is unrelated to this (it
has to do with the underlying UCM implementation on top of config specs,
and not the directory versioning model).
Although the RTC directory versioning model avoids most directory merge
conflicts, the directory conflicts that it avoids are all trivially
mergeable, so don't usually result in any significant problems in ClearCase.
Cheers,
Geoff
On 10/25/2011 1:38 PM, hujirong wrote:
has to do with the underlying UCM implementation on top of config specs,
and not the directory versioning model).
Although the RTC directory versioning model avoids most directory merge
conflicts, the directory conflicts that it avoids are all trivially
mergeable, so don't usually result in any significant problems in ClearCase.
Cheers,
Geoff
On 10/25/2011 1:38 PM, hujirong wrote:
gmclemmwrote:
RTC does not yet support a version tree for directories.
But even if it did, you wouldn't see the same structure as you would
see
in ClearCase, because in RTC, a file/directory version knows its
parent
(and knows the name of its parent), while in ClearCase, it is the
directory version that knows about its children.
So in RTC, you only get a new version of a directory if you move or
rename that directory, whereas if you move/rename a member of that
directory, you'd get a new version of that member.
Cheers,
Geoff
Thanks, I guess this change is to resolve the notorious activity
dependency issue in CC.
Jirong