backdiff
December 4, 2007
Every morning, when I come to work and login into the development server, I have a script that shows me all the files that have changed during the previous day.
Since I want to keep myself updated with what's happening in other corners of our system, I end up repeatedly typing 'cvs status' followed by 'cvs diff -r' to check the latest changes in files.
A few days ago I got tired of this extra work, so I wrote the following script: backdiff.
It runs like that:
backdiff <file>
which shows what changed in that file upon the last cvs commit. Or:
backdiff -c X <file>
showing the changes across the last X cvs commits.
Since I want to keep myself updated with what's happening in other corners of our system, I end up repeatedly typing 'cvs status' followed by 'cvs diff -r
A few days ago I got tired of this extra work, so I wrote the following script: backdiff.
It runs like that:
backdiff <file>
which shows what changed in that file upon the last cvs commit. Or:
backdiff -c X <file>
showing the changes across the last X cvs commits.
