It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,844

question asked: Oct 25 '11, 10:49 a.m.
question was seen: 4,578 times
last updated: Oct 25 '11, 10:49 a.m.

Related questions

Is there a version tree in RTC?

0
Jirong Hu (1.5k●9●295●258) | asked Oct 25 '11, 10:49 a.m.
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

3 answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Geoffrey Clemm (30.1k●3●30●35) | answered Oct 25 '11, 1:07 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
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:
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
0
permanent link
Jirong Hu (1.5k●9●295●258) | answered Oct 25 '11, 1:26 p.m.
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
0
permanent link
Geoffrey Clemm (30.1k●3●30●35) | answered Oct 25 '11, 11:48 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
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:
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

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.