David Tock wrote:

OK. All I was trying to say was that the hostname default only fits one environment, and only made sense to me once I realized that it was designed for setups like yours. At that point, everything was clear.

Hmm. I do understand your perspective. But each to their own here, I think. I would have felt more comfortable if, for example, I could create a new repository, copy only valuable files (and their history) across, and then completely destroy the old repository. Without this, it feels like either you get the structure right first time, or else you've got to learn a heck of a lot about branching and deleting in order to undo the damage.

An audit trail is fine once the system is going full steam and there's a bit of expertise in using it, but at the start one needs to experiment. And I just don't have time to experiment with toy code - the system goes live on real code from day 1. Yes, I admit it's playing with fire. But that's why I'd want a low-level fire-extinguisher available.

One other thing. I was surprised to find that I couldn't map my RCS tree through to Perforce. I know there's a rcs2perf script (or somesuch name) but, if you have a look at what it does, it's a bit limited. I would have liked to be able to add RCS trees into a depot, and that didn't seem possible.

Regards

Anthony