RE: How to find the changes related to a check in?

[Arthur Barrett]

Yong,

An alternative to Russ's explanation is to use the integrated bug
tracking in CVSNT (also GPL, free, Linux/Mac/Unix/Win).

      $ cvs edit -b 123 file1.c file2.c
      $ cvs edit -b 124 file3.c file4.c
      $ cvs commit -B 123 -m "add new feature because of buyer request"

NOTE: only file1.c and file2.c are commited because they are the only
ones marked with bug 123.  Alternatively if you don't like to use cvs
edit then you can use cvs commit -b to mark the files at commit time.

You can use -b also in update so that you can merge changes to test/prod
etc by bug number too.

And the bug number ends up in the audit and log and passed to triggers
etc.

If you would like to contribute to the open source CVSNT project, they
may be contacted via the newsgroup:
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt
or
news://news.cvsnt.org/support.cvsnt


Regards,


Arthur