As I can read in CVS manual, new file added to a module should obtain major revision number eqal to the highest revision number in that directory (for example 2.1 if highest existing revision nubmer is 2.xx). Unfortunately it doesn't work. New file will have revision 1.1. I have noticed this strange behaviour using WinCvs 1.2 and CVS1.11.6 on the AIX5 server.
After searching info-cvs archives I found information that it's probably connected with WinCVS and not CVS itself. However trying to add and commit a new file through pserver from another machine (unix command line and not WinCVS) didn't help. Have you any ideas how to create new files with the correct major revision number withour forcing it with commit oprions? Maybe there is a patch that will fix this problem? Regards, Krzysztof G�rbiel _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
