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.
If I got the point right this is never ever supported no more :( > -----Original Message----- > From: cvsnt-bounces at cvsnt.org > [mailto:cvsnt-bounces at cvsnt.org] On Behalf Of > cvssteve at diablo-technologies.com > Sent: Donnerstag, 3. November 2005 16:28 > To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook > Subject: RE: [cvsnt] Assigning revision > > A quick related question on this topic. > > Historically I've used CVS to develop ASIC RTL. We do not > check in the code on the MAIN trunk, but rather on a branch. > This model works extremely well for ASICs, (I doubt it would > work with software development). > Once we get to the end of a project, I merge the code back to > the main trunk and re-branch so that both revisions of the > ASIC can continue. > To keep the Branch numbers sensible (i.e. First ASIC on 1.1.2 > and second on 2.1.2, I commit the merges specifically to revision 2.1. > I used something like "cvs commit -f -r2.1 ..." although I > can't remember exactly. > > Are you saying that this is no longer possible with CVSNT? > > -----Original Message----- > From: cvsnt-bounces at cvsnt.org > [mailto:cvsnt-bounces at cvsnt.org] On Behalf Of Bo Berglund > Sent: November 2, 2005 3:42 AM > 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 > > _______________________________________________ > 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.