Tate Austin wrote: > version tag was. Then generate a patch based on that? So the > idea being that every time we perform a release, it marks > that release in CVS and so the next release it finds the > difference between the current files and the state the files > were in at the last tag in the cvs repository? Is this > something cvs is capable of doing by default? (i'm new to > using it beyond a distant file repository purpose) Check out... er, that is, have a look at taginfo - it may do what you want:
https://www.cvshome.org/docs/manual/cvs-1.11.19/cvs_18.html#SEC177 -- Jim Hyslop Senior Software Designer Leitch Technology International Inc. ( http://www.leitch.com ) Columnist, C/C++ Users Journal ( http://www.cuj.com/experts ) _______________________________________________ Info-cvs mailing list [email protected] http://lists.gnu.org/mailman/listinfo/info-cvs
