No I didn't see that kind of requirement before.
Note that if an activity is part of a deliver, you will end up with a "deliver.xxx" activity in the destination Stream, with only one comment associated with that deliver (losing all the comments associated with the initial activities delivered)
So you need indeed to use lsact -contrib
, following the technote "swg21136012: Activities delivered since the last baseline"
run the following command to determine what activities have been delivered since the baselines creation:
%> cleartool diffbl -activities baseline:REL1.3.117 stream:integration_stream@/vobstore/pvob deliver.development_steam.20010824.08050
>> deliver.development_steam.20010824.080503 "deliver development_steam on 08/24/01 08:05:03."
>> deliver.development_steam.20010824.080802 "deliver development_steam on 08/24/01 08:08:02."
>> ...
The above output will display the integration activities associated with the deliver operations to that stream.
If you would like to obtain a list of contributing activities for the associated integration activities, the following command can be issued for each integration activity respectively:
Example:
%> cleartool lsact -contrib activity:deliver.development_steam.20010824.080503@/vobstore/pvob
Combining that with fmt_ccase
(the -fmt
option you mentioned) will allow you, for each activity, to display only what is of interest (the Activity id and its comment, in order to grep for your keyword).
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…