The reference on “composite Baselines” is: “Best practices for using composite baselines in UCM“. Introduced in ClearCase v2002, composite baselines are a mechanism for grouping baselines into a collection. One baseline is designated as the composite, and other baselines become members of the composite You do not necessarily have to use composite baselines when you … Read more
No: Since B1 exists, all activities are “linked” by a common “timeline”, and ClearCase will ask you to also include A2. A possible solution would be to create a sub-stream, and to make a findmerge with only A1 and A3 (a findmerge is a non-UCM merge that can still take a list of UCM activities … Read more
You can simply remove the version 0 of that element (that I detail here). That will remove the associated branch. cleartool rmver file@@/main/aBranch/0 You would need to “cleartool find” all elements with a version 0 (and no version 1), and rmver those version 0. For a given branch, this would return all the versions to … Read more
This is a cleartool find request with a time-based directive from the query language: (See Additional examples of the cleartool find command) cleartool find <vobtag> -element “{created_since(target-data-time)}” -print That will list elements (instead of versions, which would display many checkins versions for every file) This should work for snapshot or dynamic views, UCM or not … Read more
Actually, when I look at the version tree, the source of the conflict during the rebase is clear: When you re-read the way ClearCase 3-way merge works, you see it needs to go back in the version tree in order to find a common ancestor to: the source (Int/2) the destination (B/1) That common ancestor … Read more
cleartool find is a good start. You can execute those anywhere within your (snapshot or dynamic) view To generate the list of those elements which contain a version with a predetermined label (REL1) attached, use the following syntax of the cleartool find command: UNIX and Linux: % cleartool find -all -element ‘{lbtype_sub(REL1)}’ -print Windows: cleartool … Read more
You can quickly list all files from a particular branch: cleartool find . -type f -branch “brtype(abranch)” -print I would recommend combining that with: -user to limit to a particular user, in case several users use the same branch. cleartool find . -type f -branch “brtype(abranch)” -user aloginname -print -created_since filter, to find all elements … Read more
Do not forget the time directive of selection rule. element /myPath/… /main/{!created_since(16-Sep-2009)} element /myPath/… /main/LATEST Can enable you to see versions from a month ago (see time and query) See also “time-based rule” answer. From there you can branch and update your code from this older stable point.
individual stream for each developer under DV stream Whoât???? This is SPARTA! (err… no: madness: this is madness) A stream represents a development effort, not a sandbox for a “resource” (i.e. “a developer”). Resources come and go, development tasks stay. You should have a stream per development line, upon which many developers create their own … Read more
A first possibility would be to try and select the correct version of the sub-directory to revert, like: element /path/to/directory /main/[branch]/[version] But that would be plain wrong, because: extended path names is not supported in snapshot view, as explained in this SO question. to select the directory alone is not enough (the files would still … Read more