>Likewise.. > >cvs update -j TEST -j DEV -m > >means migrate changes from TEST to DEV, and remember the migration. >Then, if, inside head: > >cvs update -j TEST -m > >this would migrate the TEST changes into head... on a > >cvs update -j DEV -m > >it would remember that the DEV changes have already been put into >test... etc. etc.
You could write scripts that do that with moving and creating new tags. So every time you call the mmerge script it will apply a tag like MERGED_DATE and there is a second tag LAST_MERGE which will be moved to the new position. That way you will have a list of all merge points and also the point of the last merge. Once you have the scripts the call is as easy as cvs update -m. bye Fabi _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
