[Top][All Lists]

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

Re: assigning revisions

From: Larry Jones
Subject: Re: assigning revisions
Date: Thu, 5 Sep 2002 10:41:53 -0400 (EDT)

Daniel Lungu writes [in very long lines]:
> Concurrent Versions System (CVS) 1.10.7 (client/server)

1.10.7 is very old -- you should consider upgrading.

> ----- error: first number in <revision> of "b" should be -----
> ----- highest first number of any file in that directory -----
> $ cvs commit b
> RCS file: /cvsroot/Soft/module/b,v
> done
> Checking in b;
> /cvsroot/Soft/module/b,v  <--  b
> initial revision: 1.1
> done

That's a subtle difference between local mode and client/server mode. 
In local mode, the command runs in your actual working directory and
does what you expect.  In client/server mode, the command actually runs
in a shadow directory on the server that contains just the modified
files (which in this case is just b).  Revision numbers are for CVS's
internal use -- you shouldn't try to mess with them or use them for your
own purposes: use tags instead.

> ----- furthermore: cannot commit changes to "a" anylonger -----
> $ cvs commit a
> cvs server: sticky tag `2.0' for file `a' is not a branch
> cvs [server aborted]: correct above errors first!
> cvs commit: saving log message in /tmp/cvsBAAaaLWoa

When you do a "commit -r", it sets a sticky tag on the file in your
working directory.  You need to remove that sticky tag (with "update
-A") before you can commit any additional changes.

-Larry Jones

Geez, I gotta have a REASON for everything? -- Calvin

reply via email to

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