Withers, Robert <rwithers at quallaby.com> said:
>> "cvs upd -r TESTED" would do the job of grabbing the "TESTED" release.
>
>Yes, but only if you have a single TESTED version.  I suppose you could
>retag the trunk as each version was released.  This was why I mentioned the
>history command, so one could get a list of available tags to load, per
>module.
>
The easiest way is to use the '-f' option on 'cvs tag' - this will move
existing tags, so there would indeed be only one TESTED version.

>Ok, let me see ...  got one.  How could we query the available tag/module
>combinations before we checkout?  :)
>
Not easy to do with CVS. With Trug, I tricked a bit by having a hidden file
and making sure it was modified before every CVS command; in this way, there
would be one file with a complete revision log I could query.

BTW, given Subversion (see elsewhere), we might not want to invest too much
time in CVS wizardry. Seen there, been it, ate the t-shirt.

-- 
Cees de Groot               http://www.cdegroot.com     <cg at cdegroot.com>
GnuPG 1024D/E0989E8B 0016 F679 F38D 5946 4ECD  1986 F303 937F E098 9E8B