Sticking with history, this pretty much the scenario that we developed
the audit tools for. Insofar as possible, we try to assign developers
chores that don't overlap much, but they'll inevitably have some impact
on shared code. So, if we're merging work from programmers A and B,
we'll use the audit to automatically find blocks that differ, and then
present the differences. Ideally (which isn't always, especially
nowadays) A and B are sitting next to each other and can discuss why
each did what, reconcile any compatbilities, and forge ahead. Then the
pattern can repeat with A and C (assuming A is the project leader) etc.
In my experience, this is a very common scenario. We've seen remarkably
little need to recover snapshots from the past, even though we've used
CVS for some years now. But the kind of auditing facilities that this
Audit utility then and Beyond Compare now provide are invaluable in
multi-programmer projects.
Cheers,
Elizabeth
--
==================================================
Elizabeth D. Rather (US & Canada) 800-55-FORTH
FORTH Inc. +1 310.999.6784
5959 West Century Blvd. Suite 700
Los Angeles, CA 90045
http://www.forth.com
"Forth-based products and Services for real-time
applications since 1973."
==================================================
