I'm implementing CVS into an old-fashioned System of: a) Base Code b) Staged/Tested Fixes c) Working/WOrked fixes.
All done with no control in native files. Rather than running this system like our Newer Jbuilder/CVS checkouts, we're keeping the same structure. I have it checking out and commiting and tagging, which defines a), b) and half of c). However I can't check out all Files that match the following : --- File contains a revision __after__ a given tag was applied, and current revision contains no tags, or at least not the above mentioned tag. These files would make up commited changes that were not yet completely tested, approved, and ready to ship. I would like to be able to recursively do this with one cvs command...... Any suggestions, either within a cvs command, or a wrapper which determines what to check out.... (BTW, I'm not suggesting this is a good idea, but its the best I can do with the legacy setup we have). Thanx Eric Aksomitis NOTICE: This confidential e-mail message is only for the intended recipient(s). If you are not the intended recipient, be advised that disclosing, copying, distributing, or any other use of this message, is strictly prohibited. In such case, please destroy this message and notify the sender. _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
