As explained in “Before adding files and directories to source control”, the version 0 is a placeholder marking the start for all versions in a given branch: You can end up with only the version 0 when you undo-checkout a file you just checked out in a new branch (in that case, only a version … Read more
Evil Twin An Evil Twin is an element that you have removed (using rmname) and want to re-add, but it’s ‘evil twin’ exists in previous versions of the directory. You have to remember that each element had a unique ID, so you are attempting to add an element with the same name – but with … Read more
I’m trying to look at a bunch of old versions I am not sure if you are speaking about “a bunch of old versions” of one file, “a bunch of old versions” from several files. To visualize several old versions of one file, the simplest mean is to display its version tree (ct lsvtree -graph … Read more
It will contain all changes. Except an incremental baselines will compute those changes by adding: unique modifications introduced by the few changes (that is what an “incremental baseline” is: a label set only on the new versions since the previous baseline) all the other changes already references by the previous baselines up to a full … Read more
Snapshot views are based on the local filesystem (like a workspace in Subversion): you load files anywhere you want on your hard drive you have to ‘cleartool update‘ to refresh its content Dynamic views are based on network content: they represent the dynamic (as in “always refreshed”) view of a network content (the remote VOB … Read more
Core concepts? centralized(-replicated) VCS: ClearCase is halfway between the centralized VCS world (one or several “centralized” repos or VOBS – Version Object Bases – every developer must access to commit) and the distributed VCS world. But it also supports a “replicated” mode allowing you to replicate a repo in a distant site (MultiSite ClearCase), sending … Read more