![jrep's picture jrep's picture](https://www.cmcrossroads.com/sites/default/themes/techwell/images/user_icon_default.jpg)
Not sure I completely understand your use case, but you can write the config spec based on date/time, does that help? If you're using clear make and configuration records, you can also write the cspec based on a specified D.O.
If i have 5 versions, config spec should point me to 4th version.
it should happen to all files, so i cannot use LABEL.
Thanks in advance.
Thanks,
Ramana
Not sure I completely understand your use case, but you can write the config spec based on date/time, does that help? If you're using clear make and configuration records, you can also write the cspec based on a specified D.O.
Hi jrep,
Thanks for your prompt reply, but this is not what i am looking.
please see below example:
if a have a element with 3 versions like below.
file1@@/main/1
file1@@main/2
file1@@main/3 --LATEST
now i should set config spec to point to file1@@/main/2
it is not only to this file, but to all files.
if one more version gets created to file1 i.e file@@/main/4, then it CS should point to file@@/main/3
thanks,
Ramana
why oh why do you need this?
There isn't a good CM practice that uses something like that. If you want to be able to go back to something, you baseline or label it.
I am a bit new to CC and have used CVS. Incase of CVS, we can update a local copy of any element explicitly to say version 2 using update option where are in CC / CCRC I don't that options.
i suppose we would have to use the config spec to
element -file <VOB-loc-to-file> /main/<revision-Number>
i would have to check it though...
Ajit G.