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.
Why not create tags that match the PVCS version ids, then you don't need to worry about CVS revision numbers. Given that tags need to start with a letter and can't include dots you'll need to change them to something else, eg change 3.1 to Pvcs_3_1. Helpfully, Occasionally, Richard. -----Original Message----- From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org] On Behalf Of Bo Berglund Sent: Wednesday, November 02, 2005 1:29 PM To: Remo Liechti Cc: CVS-NT Mailing list (E-mail) Subject: RE: [cvsnt] Assigning revision I have absolutely no knowledge of PVCS.... /Bo -----Original Message----- From: Remo Liechti [mailto:remo.liechti at swisslog.com] Sent: den 2 november 2005 13:31 To: Bo Berglund Subject: RE: [cvsnt] Assigning revision Hi Bo Well, we are moving from PVCS to CVS and I need to have exactly the same revision number of a file in cvs as it is in pvcs... Thats the matter why I need to be able to set the revsion number... There are tags like our product release number set on these files, they have to be ecatly the same as in the pvcs too. Is it possible to set multiple tags or something like this? I'm not able to try this now cause the cvs server is down for maintanance... Thank you very much! Remo > -----Original Message----- > From: Bo Berglund [mailto:Bo.Berglund at system3r.se] > Sent: Mittwoch, 2. November 2005 13:15 > To: Remo Liechti > Subject: RE: [cvsnt] Assigning revision > > It is *NOT* stupid to assign releases via tags, in fact this is the > only sensible way to do it. The reason is simply that each and every > edit you do on a file and commit will cause the revision number to > step up. If you have more than one single file in your project you > will never be able to edit all exactly the same number of times. > Thus the files in your project will always have different revision > numbers at any given point in time (for example when you do the > release). > > Here is where tagging comes in. A tag is placed on the whold project > so that *all* files are tagged with the exact same tag, which should > be a bit descriptive like > REL_MyProgram_Ver_1-0-2-23_2005-111-03 or similar. > > Now every file records this tag in the current revision and then later > you can easily restore the whole project to this state by updating to > the tag. For example if you need to do some maintenence work on an old > release. > > Tags is what you *should use*! > > /Bo > > -----Original Message----- > From: Remo Liechti [mailto:remo.liechti at swisslog.com] > Sent: den 2 november 2005 09:47 > To: Bo Berglund > Subject: RE: [cvsnt] Assigning revision > > > Ah okay. Thank for the help. > > But it is possible to go up to the 2.1 revision number by some tagging > or something similar? > I think it's really stupid if you are not able to set a file to a new > release number through the revision number. Sure, it would be possible > to do releasing using the tags. But these tags have to start with a > letter and are not allowed to contain '.'(dots) in it... > > What shall I do? > > Remo > > > > -----Original Message----- > > From: Bo Berglund [mailto:Bo.Berglund at system3r.se] > > Sent: Mittwoch, 2. November 2005 09:42 > > To: Remo Liechti; cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook > > Subject: RE: [cvsnt] Assigning revision > > > > You should NEVER EVER interfere with the file revision numbers! > > These are really internal CVS data to keep track of the changes of > > files. You have no sensible way of using these and so you > should not > > try to set them either. > > > > That is also why CVSNT has removed support for changing > them like you > > tried to do in recent versions. The capability still exists > in GNU CVS > > by what I understand, but it is no less of a danger there. > > > > Furthermore, revision numbers with zeros are *for special cvs use > > only*!!! > > They are so called nagic revisions and are used by cvs to > keep track > > of things like branches etc. Never to be used by the cvs user.... > > > > /Bo > > > > > > -----Original Message----- > > From: cvsnt-bounces at cvsnt.org > > [mailto:cvsnt-bounces at cvsnt.org]On Behalf Of Remo Liechti > > Sent: den 2 november 2005 08:36 > > To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook > > Subject: [cvsnt] Assigning revision > > > > > > Hi there > > I'm using WinCVS. Now I got a file with the revision number > 1.36, and > > I need to change only this file to 2.0. > > In a CVS book I read that this is possible using: > > cvs -r commit -m myMessage -r 2.0 -- "MyDocument" > > > > If I do so, I got the error: > > cvs commit: warning: unrecognized response `cvs server: > > invalid option -- r' from cvs server > > > > Seems like cvsNT does not support the forcing of a revision no more. > > What to do? > > > > Thanks, > > Remo > > > > ____________________________________________________________ > > This message may contain legally privileged or confidential > > information and is therefore addressed to the named persons only. > > The recipient should inform the sender and delete this message, if > > he/she is not named as addressee. > > The sender disclaims any and all liability for the integrity and > > punctuality of this message. > > The sender has activated an automatic virus scanning by > Messagelabs, > > but does not guarantee the virus free transmission of this message. > > _______________________________________________ > > cvsnt mailing list > > cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook > > http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs > > > > ____________________________________________________________ > > This message has been checked for all known viruses by Messagelabs. > > > > ____________________________________________________________ > This message may contain legally privileged or confidential > information and is therefore addressed to the named persons only. > The recipient should inform the sender and delete this message, if > he/she is not named as addressee. > The sender disclaims any and all liability for the integrity and > punctuality of this message. > The sender has activated an automatic virus scanning by Messagelabs, > but does not guarantee the virus free transmission of this message. > > ____________________________________________________________ > This message has been checked for all known viruses by Messagelabs. > ____________________________________________________________ This message may contain legally privileged or confidential information and is therefore addressed to the named persons only. The recipient should inform the sender and delete this message, if he/she is not named as addressee. The sender disclaims any and all liability for the integrity and punctuality of this message. The sender has activated an automatic virus scanning by Messagelabs, but does not guarantee the virus free transmission of this message. _______________________________________________ cvsnt mailing list cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs http://www.bbc.co.uk/ This e-mail (and any attachments) is confidential and may contain personal views which are not the views of the BBC unless specifically stated. If you have received it in error, please delete it from your system. Do not use, copy or disclose the information in any way nor act in reliance on it and notify the sender immediately. Please note that the BBC monitors e-mails sent or received. Further communication will signify your consent to this.