[Cvsnt] Commiting changed file with siticky revsion

[TCzarnecki at abc.com.pl]

I've tried to check what will happen if someone:
1. Updates a file with sticky revision (e.g. 2.o while most up to date
revision is 2.5)
2. Modifies it
3. Commits it
I expect either an error message telling that such operation is not allowed
or new revision created (2.6).
With CVSNT i get:

cvs [commit aborted]: end of file from server (consult above messages if
any)

Please tell me what should the behaviour look like. I think this is a bug.

T.



_______________________________________________
Cvsnt mailing list
Cvsnt at cvsnt.org
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt