You could try
cvs diff --brief -r rev1 -r rev2 ...
That will tell you which files have changed and use the output to
build a script to get all the changed files.
It also sounds like you've a configuration management problem in the
way you do database changes. Because you are changing the state of an
existing live database, it would be wiser to have only file per
release to change the database. And testing this file is pretty easy
because you always test against a copy of the current live database.
If you have lots of files per database per release, you're bound to
screw by leaving accidentially one out. Hence the reason for your
original question.
Chris
--
Chris Velevitch
Manager - Sydney Flash Developers Group
www.flashdev.org.au
---
You are currently subscribed to cfaussie as: [email protected]
To unsubscribe send a blank email to [EMAIL PROTECTED]
Aussie Macromedia Developers: http://lists.daemon.com.au/
