I have a few friends that still use RCS for their version control needs. We have argued over various points between RCS and Git, and as far as I can tell the one thing RCS has that Git does not is a locking mechanism. That is to say, co -l checks out a file and also gives you a lock on it, preventing others from futzing with it, and ci -u checks in the file and releases your lock. This is useful if you have a shared working copy on a multiuser system or on a network file system, and you don't want conflicts. I was wondering if there would be interest in such a feature on the Git developers side. Cheers, Edward -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html