[Gusdev-gusdev] cvsmod: helpful little tool

[Steve F. <st...@pc...>]

folks-

i have a teeny little tool which helps us keep our cvs repository well 
commented.

one of the big problems in documenting your changes in cvs is this:  you 
have been working on a few things that are not really related.  and now 
you want to check in your stuff.  the easiest way is:
   %cd $PROJECT_HOME/GUS      #eg, go to the root of your module
   %cvs commit -m "some comment here, or... worse, none at all"

The problem is that you are commenting ALL the files you have changed, 
but they aren't all related.

An alternative approach, and probably the best, is to use emac's version 
control tools to check in your files individually, as soon as you make 
changes.  however, that doesn't work if you are hitting a bunch of files 
and are in a develop/debug loop.

So, i use cvsmod.

All it does is give you a report of the files that you have changed:

[sfischer@pythia GUS]$ cvsmod
File: DialogFactoryPlasmoDB.java        Status: Locally Modified
File: QueryHistoryPage.java     Status: Locally Modified
File: QueryPage.java    Status: Locally Modified
File: SQLIdResultTable.java     Status: Locally Modified
File: reportMaker.pl.in Status: Locally Modified
File: rnaSimilarityPng.pm.in    Status: Locally Modified

Then, you can do individualized check-ins for one or more of those 
files, giving them the proper comment.

When you are all done, cvsmod will not return any files that have been 
modified.

And, the best part is that cvsmod is utterly trivial.  Here it is:

#!/bin/csh
cvs status |& grep Modified

I have put it into my local bin.  If you are at CBIL,you can copy it from:
/home/sfischer/mybin/cvsmod

Steve