[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Controlling revision (version number)

From: Jean Tourrilhes
Subject: Controlling revision (version number)
Date: Tue, 6 Mar 2001 16:18:25 -0800
User-agent: Mutt/1.2.5i


        (I'm not on the mailing list)

        I've recently put a project that I was maintaining into a CVS
repository (as part of a bigger project). CVS is driving me nuts with
the revision numbers. The result is that all version numbers in the
CVS repository are all over the place. Yuck !

        When I started, my project was a revision 2.4.3 (my own
revision numbers). I did a cvs import, used the -b flag, and
everything was put in CVS at revision Strange, but not too
        I did a bit of hacking, added new files and co. I tried to do
a "cvs update ; cvs commit -r 2.4.4", but it refused :
                cvs server: Up-to-date check failed for XXX (all my files)
        So, I did a "cvs commit". And now, I have files with revision
2.5, some with and some other with 1.1.
        Modified a few files to try, and now I have 2.6, 2.5,,
1.2 and 1.1 revisions all mixed up :-(
        Reread the man page, mention the "cvs tag" stuff that is
necessary for the -r option. So, I try a "cvs tag -b 2.4.4". It fail
saying that tag must start with a letter. Argh !

        So please : could somebody be kind enough to tell me how to
control revision number with CVS ? I want to put all new and modified
files at revision 2.4.4, which is what it should be. Why does it have
to be so difficult ?

        Thanks in advance...


reply via email to

[Prev in Thread] Current Thread [Next in Thread]