Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
Raghu,
I don't see any problems.
I just issued a command in my sandbox like this:
cvs update -r 1.28 myprog.exe
(HEAD revision of myprog.exe is 1.30)
and the update just produced a single new file myprog.exe which
replaced the existing one. No other files created at all.
Which is really what I would expect.
/Bo
(I am now going off-line for a week)
-----Original Message-----
From: Raghuram Nanda [mailto:raghuexcels at rediffmail.com]
Sent: den 10 juni 2003 11:17
To: Bo Berglund
Subject: Re: RE: [cvsnt] Problem retrieving doc files
Hi bo,
I am currently downloading all the latest version softwares.
Then regarding the command which you have said, was not what I
want/meant.
The command to RETRIEVE earlier REVISION of a file is also
update -r #verno filename
(pls note the flag -r ...)
In this case, this command will retrieve the said verno file and
will put the same in the checkedout folder with name
filename.#.verno.
I wanted info reg this command to retrieve binary files
properly.
I know the purpose,content, and situation in which cvs creates
file like: .#.originalfilename.doc.1.3
Regards,
Raghu.
On Tue, 10 Jun 2003 Bo Berglund wrote :
>WinCvs version
>If you don't use the latest version then please download and
>install.
>There has been an update options tab on the dialogue that comes
>up
>when you click the update button for a long time now.
>Help/About in my WinCvs shows version as 1.3.13.1 Beta 13 (Build
>1)
>
>CVS version
>Using the command cvs ver (from WinCvs inside a sandbox) shows
>something
>like this:
>Server: Concurrent Versions System (CVSNT) 2.0.0
>(client/server)
>Client: Concurrent Versions System (CVSNT) 2.0.2
>(client/server)
>
>Typing cvs --v on the command window in a non-cvs folder:
>C:\>cvs --v
>
>Concurrent Versions System (CVSNT) 1.11.1.3 (Daily Snapshot
>Build 57l) (client/server)
>
>As you can see in my case the command window uses a different
>version of CVS than
>WinCvs. This is because in WinCvs the CVS.exe to use is defined,
>but on the command line
>it comes from the path setting.
>
>CVSNT
>If you get versions like 1.11 or something similar then you
>should go to
>www.cvsnt.org and download the latest 2.0 setup and install it.
>
>Update operation
>What cvs update should do is to replace the file already in your
>sandbox with the
>one from the server. This is normal.
>But if it detects that the file has been edited by you, then it
>automatically renames the
>edited file to something like: .#.originalfilename.doc.1.3
>(where 1.3 is the revision your
>edits started out from).
>So your edited data are saved in a renamed file and the working
>file will hold the old revision.
>
>/Bo
>