This area is an archive and is no longer actively maintained. Information found on this page is likely to be extremely out of date and therefore highly inaccurate. We recommend the Ximbiot - CVS Wiki for up-to-date information about CVS and its associtated tools.

If you do find anything useful on this page that is not yet in the Ximbiot - CVS Wiki and you have the time, please add it!

CVShome.org

Tracking Changes


Discussion:

This is a discussion on how to track "changes" through a development process or see the history of what was modified as part of each change.

Some aspects of change control can be handled completely outside CVS using a tracking system such as GNATS or Jitterbug. One way to connect such a system to CVS is to require CVS log messages to contain a valid bug number. For details, see the CVS documentation for the "verifymsg" feature of CVS.

To remember that checkins to several files were made as part of the same logical change with CVS, create a tag before and after each checkin (generally via some kind of custom front-end to CVS).


For More Information:
  • One nice example of a system built on top of tags is Undernet (it uses a slight variation of the before and after tags - an after tag plus a checkin to the dummy file ".patches" which keeps track of the order of the changes).
  • Aegis is a configuration management system with better support for changes than CVS has.

Return to The Information Page List.

Derek Price, CVS developer and technical editor of Essential CVS (Essentials line from O'Reilly Press) , and others offer consulting services and training through Ximbiot.