next message in archive
next message in thread
previous message in archive
Index of Subjects
Thanks everyone for the speedy responses! Obviously there's a significant ammount of interest in the subject. In addition to the replies that have gone to the lists I've received one reply from an IP editor who is personally a very strong supporter of RCS. --- In the past we've always tried to give users an opportunity to retain a old familiar way of doing things while introducing new services. Clearly IP's who have never used the old editing systems are more likely to have a problem if they 'bump' into RCS files, locks, etc... However if we are going to allow individuals a choice we need a relatively foolproof way of ensuring that RCS does not creep into directories where RCS is clearly not wanted. This has me thnking about using a .no_rcs file type mechanism. and/or a nightly 'clean out the RCS for registered directories' script or some such mechanism... there's a couple of ways of doing it... I'm out of town for a couple of days and although I'll be checking email I won't be quite as accessible for about 10 days. david potter
next message in archive
next message in thread
previous message in archive
Index of Subjects