Is it possible in clearcase to checkout a file for modification such that it is impossible to check it back in? I’m going to be hacking some files on a private branch, only some of which I want to ever check in. I want to eliminate the possibility of accidentally checking in unwanted changes. (I know we can write a trigger to check for magic keywords in the checkout comment; I'm look for something built-in to CC.)
相关问题
- How to restrict VOB read access in ClearCase (Wind
- preserving history when using mercurial ontop of c
- How to use ClearCase annotate sub-command?
- listing files checked in during last 2 days
- VS2008 and ClearCase : opening solution requests a
相关文章
- Provide version to independent files in clearcase
- How to undo checkout a file checked out from anoth
- Getting present working view in Clearcase
- What is the nature of a “MVFS filesystem” with Cle
- How to list only the name of the baselines in UCM
- Reuse a ClearCase view
- Value of using Git with ClearCase, AccuRev or Perf
- ClearCase: change branch type name?
"Hacking some files" is spelled in ClearCase lingo: hijacked files in a snapshot view.
All you have to do is to:
cleartool lock -nusers userA,userB,... aFile
)The OP Kevin Little adds in the comment:
Easy enough:
"Hacking some files" is also spelled in ClearCase lingo: eclipsed files in a dynamic view.
All you have to do is to:
cleartool lock -nusers userA,userB,... aFile
)To not select them, add to the config spec (
ct edcs
) before the other rules:To restore them, all you have to do is move or remove those files.
They will be dynamically be replaced by their original and still versioned element.
I don't know about the administration. From a user standpoint, you could have 2 views. In one view, checkout the files you don't want to check in. In the other view (your view), check them out unreserved. Then, if you try to check them in, you'll get an error because they're checked out to the other view.