[cvsnt] Re: Forcing a revision....

[Bo Berglund]

So I tested on our production server as well and it worked just fine...
It seems like there is a difference between the test server I use and
our production server. The production server shows this:
Client: Concurrent Versions System (CVSNT) 2.0.34 (client/server)
Server: Concurrent Versions System (CVSNT) 2.0.41 (client/server)

but the combination I use when testing at home is:
Client: Concurrent Versions System (CVSNT) 2.0.41a (client/server)
Server: Concurrent Versions System (CVSNT) 2.0.51 (client/server)

So somehow between these versions there is a bug introduced that
refuses to accept the revision bumping command cvs commit -r <newrev>

/Bo B

-----Original Message-----
From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org]On Behalf
Of Elisa Cargnel
Sent: den 19 augusti 2004 09:32
To: cvsnt at cvsnt.org
Subject: [cvsnt] Re: Forcing a revision....


> In order to suggest a solution to the guy who really wants to bump the
> revisions of his files by incrementing the major digit I tested the
> cvs co -r <rev> command to see what would happen.
> I did it from within WinCvs and the result is somewhat surprising:
>
> cvs -z9 commit -m "testing revision forcing" -r 2.1 ModuleYYdoc.txt
> (in directory F:\Engineering\Projects\Bosse\ModuleYY\)
> Checking in ModuleYYdoc.txt;
> cvs [server aborted]: revision `2.1' does not exist

Hi,
I tried with:

cvs commit -m "no message" -r 2.1 NuovoDoc.txt (in directory
D:\ProgettiCVS\Telegestione\Documentazione\CM\)

And it did works fine.
nice point, It will be useful!
Thank you.
elisa

Client: Win Concurrent Versions System 1.3.14.1 Beta 14
Server: Concurrent Versions System (CVSNT) 2.0.51 (client/server)



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