[ On Wednesday, September 29, 2004 at 08:33:40 (-0700), Yamuna Ramasubramaniyan wrote: ] > Subject: Using moving tags (Was: Preventing "dirty" checkins) > > I have a question about using moving tags. You tag > the repository with LAST_GOOD today. Someone removes > a file. This file still contains the LAST_GOOD tag. > The next person checking out the module with the > LAST_GOOD tag will get this deleted file. Do you use > a commitinfo trigger to remove the moving tag from the > deleted file? Are there any other ways to handle this > case?
Create a new "feature" (or "fix") branch for every change (and clean up old feature/fix branches once they're also integrated onto a release branch). Merge the feature/fix branches to the trunk for integration into the main line of active development (and then optionally cut release branches onto which fix branches can optionally be merged to as well). You can even make a rule that only supervisors are allowed to commit to the trunk and/or to release branches and thus only supervisors will be allowed to approve changes to the baseline or to a patch release. Supervisors can further be required to do compiles and run regression tests before committing the integrated changes. However this is all extremely complicated to manage, especially without the help of some front-end/wrapper tools. CVS really is not the right tool for this style of development. -- Greg A. Woods +1 416 218-0098 VE3TCP RoboHack <[EMAIL PROTECTED]> Planix, Inc. <[EMAIL PROTECTED]> Secrets of the Weird <[EMAIL PROTECTED]> _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs