Matthias Kaeppler wrote: > > Sergei Organov wrote: > > Matthias Kaeppler <[EMAIL PROTECTED]> writes: <SNIP> > >>It would be a lot better, if the versioning would happen on the module base, > >>i.e. you can commit the content of your sandbox as a new version of your > >>program rather than new versions of the individual files. > >> > >> > >>Is that possible somehow? I can't find any means at all in the documentation > >>to keep track and control the /program/ version instead of the individual > >>source file revisions. > > > > > > "cvs tag" is your friend: > > > > <quote manual> <SNIP> > > </quote manual> > Ah okay, thanks for pointing me to the right direction. > I'll read up on tagging and come back if I have further questions. In anticipation of what I expect your next question to be: CVS keeps the checkin logs with each individual file, how do I get a log that shows a coherent picture of each checkin?
Please see cvs2cl: http://www.red-bean.com/cvs2cl/ There may be other tools to do it, but this one is my favorite. -- Todd Denniston Crane Division, Naval Surface Warfare Center (NSWC Crane) Harnessing the Power of Technology for the Warfighter _______________________________________________ Info-cvs mailing list [email protected] http://lists.gnu.org/mailman/listinfo/info-cvs
