Reputation: 384
Imagine a scenario where your config spec looks something like the following:
element * CHECKEDOUT
element * .../branch_two/LATEST
element * .../branch_one/LATEST -mkbranch branch_two
element * BASE_LABEL -mkbranch branch_one
I'd like to see what a co
command would actually do, i.e. see all the branches it would create when checking out a file, without actually checking out the file (for one reason or another, we don't have a trigger set up to automatically delete lone version 0s of files on a branch, so manually cleaning them up is a hassle & very stressful). This is a relatively simple example, but your config spec can grow to be quite large & mistakes can certainly happen while writing it. Given that I'm no expert in Clearcase, I'd really benefit from a way to verify that my config spec is written correctly.
ct ls
helps, but it only lets you see "one level down," so to speak. I think maybe ct co -query
is supposed to perform this role, but when I tried it on my machine, I just got the standard ct co
behavior, as if the flag wasn't there, so I'm not sure if there's another way to go about this.
Upvotes: 1
Views: 73
Reputation: 1329622
I don't see that feature native in ClearCase.
Which mean you would to:
ct unco
, removing any 0 placeholder versionBut in general when it comes to checkout, I don't know of a "preview" option.
Upvotes: 1