Mark K wrote...

>The next step is to do your port, test and get things ready for release.

During your porting work, you can always see whether you did
some modifications to a given file(set) and -if so- what the
changes compared to the original/older versions are...

 $ cvs status -v somefile.c

 $ cvs diff -u somefile.c

When you commit/checkin working source code versions into the
cvs repository at certain points in time, you can even perform
diffs referring to different versions. Here the tags also come
in handy (Mark used V8_11_3 for the initial check-in)...

 $ cvs diff -u -r V8_11_3 somefile.c

GNU cvs is quite handy to keep track of or undo/redo changes.

Lars.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *