StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>The thing is, a view doesn't point to <em>one</em> branch.<br> It only combines various element selection rules in the config spec, which makes it reflect a version on a branch at a given time, for a given tree/file.<br> See:</p> <ul> <li><a href="https://stackoverflow.com/questions/3296930/how-would-you-select-versions-from-a-specific-branch-in-clearcase/3297002#3297002">How would you select versions from a specific branch in ClearCase?</a> for a concrete example. </li> <li><a href="https://stackoverflow.com/questions/996274/how-best-to-branch-in-clearcase/997607#997607">How best to branch in Clearcase?</a> to see how branches work.</li> </ul> <p>See also the debate on <a href="https://stackoverflow.com/questions/763099/flexible-vs-static-branching-git-vs-clearcase-accurev/764219#764219">selection by composition vs. selection by revision</a> to better understand why, by default, a ClearCase config spec doesn't necessary reference one branch.</p> <p>The simpler way to check what is the <em>current</em> branch is:</p> <ul> <li><code>cd /my/view/path/to/relevant/directory</code></li> <li><code>cleartool ls</code></li> </ul> <p>Example:</p> <pre><code>C:\views\myView\path\to\dir>cleartool ls .checkstyle@@\main\MY_BRANCH_Dev\4 Rule: ...\MY_BRANCH_Dev\LATEST .classpath@@\main\MY_BRANCH_Int\ADV_ACC_Dev\1 Rule: ...\MY_BRANCH_Dev\LATEST .classycle@@\main\MY_BRANCH_Int\ADV_ACC_Dev\0 Rule: ...\MY_BRANCH_Dev\LATEST </code></pre> <p>That view, for the <code>path/to/relevant/directory</code> path, point to branch <code>MY_BRANCH_Dev</code></p> <hr> <p>Note: With ClearCase UCM, this is simpler:</p> <pre><code>cleartool lsstream -cview </code></pre> <p>will give you the name of the name of the Stream (and by extension, the associated branch) on which the views points to.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload