clearcase

I am looping through a list of clearcase files to see if the text "Merge <-" is not part of the output of ct describe . I have tried running a while loop on this list of clearcase files then appending it to another file if it meets my desired condition. Below is the exact logic I used: 16 FILTER_LIST=cut -f1 -d'@' branchmerge_versions.txt 17 touch temp.txt 18 echo $FILTER_LIST > temp.txt 19 20 while read t; do 21 isMerged=`cleartool describe t | grep -e "Merge <-"` 22 if [[ "x$isMerged" == "x" ]]; then 23 echo "$t" >> filesToMerge.txt 24 fi 25 done < temp.txt 26 Running bash -n on the script

I am trying to run the following code, but the got #error 1 at startview command, and #error 2 in desc command. use Win32::OLE; $ct = Win32::OLE->new('ClearCase.ClearTool') or die "Could not create ClearTool object\n"; $view = "ccadm01_UARK_DEV"; $output = $ct->CmdExec("pwv") or die("Cleartool returned error: ", Win32::OLE->LastError(), "\n"); print ("pwv \$output = $output\n"); # error 1 : cleartool return error 0 $output = $ct->CmdExec("startview ccadm01_UARK_DEV") or die("Cleartool returned error: ", Win32::OLE->LastError(), "\n"); $CWD = $view_dir; print( "Current directory: $CWD\n"); #

when baselines are obsolete will it have any ill-effect? For example if the baseline was already rebased by many, if i obsolete the baseline what will happen? You can, but shouldn't obsolete a baseline which is currently used as a foundation baseline on an existing stream. Even if it is possible, it used to have some side-effects like: stopping other baselines from being seen by the " lsbl " command ( swg1IC42113 , fixed in ClearCase 7.0.x). not showing the Baselines when foundation baseline is locked or obsolete ( ss , fixed in ClearCase 7.0.x). (older ClearCase like 2003 could have an issue