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
Here’s a method that avoids hijacks, which our team used this method quite successfully for over a year, until we retired ClearCase for Subversion (per company policy, although it is a backwards step for our team – we were basically just using ClearCase as a dumb file system, and virtually working natively in git, but … 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
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
You can find a good comparison between ClearCase and Git in my SO answer: “What are the basic ClearCase concepts every developer should know?“, illustrating some major differences (and some shortcomings of ClearCase) File-centric operations The most single important shortcoming of ClearCase is its old “file-centric” approach (as opposed to “repository-centric” like in SVN or … 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
I wouldn’t recommend setting a view, because setview itself spawn a new process. I really prefer working with /view/viewTag/aVob/… after starting the view (cleartool startview viewTag ) The “spawn process” issue makes the all thing too complex in my opinion, and explains why you have technotes like: “Setting into a view from a shell script … 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
Clearcase stores its ‘files’ as directories What Aric is trying to tell you is that ClearCase uses extended path names, “extended” because it extends the file name with version path. So in a dynamic view, any file can be described to reveal its versioning path: $ ct ls myFile $ ct descr -l myFile myFile@@/main/3 … Read more
I would rather go with the clearfsimport script, better equipped to import multiple times the same set of files, and automatically: add new files, make new version of existing files previously imported (but modified in the source set of files re-imported) remove files already imported but no longer present in the source set of files. … Read more