Laird Nelson wrote:
> That said, if you know that your user will never try to force a commit
> using the -r switch (don't know how you'd know this, but most users
> don't use this flag), then you can write a commitinfo script that will
> check the old revision number and reject access based on it, making the
> assumption that the new revision number will be the old one with the
> rightmost number incremented by one. You could also check the tag.
This isn't strictly true. The first commit of a file to a branch could go
from 1.X to 1.X.Y.1.
Derek
--
Derek Price CVS Solutions Architect ( http://CVSHome.org )
mailto:[EMAIL PROTECTED] OpenAvenue ( http://OpenAvenue.com )
Cynic: Someone who smells the flowers and looks for the casket
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
