Received: from fencepost.gnu.org (fencepost.gnu.org [199.232.76.164]) by gateway.camelot.jp (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id DAA16160 for <address@hidden>; Tue, 6 Feb 2001 03:06:17 +0900
There is just the daily backup of the repository -- I do not want to redo the changes of the last day... probably the best way that's what I learned. Just for exactness: we developed some OS stuff an
maybe, restore the repository from backup, prior to the command run. -or- maybe release version 3 of your software instead of version 2, what happened to version 2 can become folklore in your company
Dear all, as I posted yesterday: Accidentaly, I set a revision to be 3.0 instead of 2.0 by issueing the command cvs commit -r 3.0 Is there any way how I can set back the revision to 2.0? cvs commit -
1. UM, if I read the help right that will DELETE the specified version. 2. Don't think that will work. 3. that might work. Note that there are some assumptions that CVS makes about version numbers an
I have a file foo at revision 1.1234. It was extensively modified and committed as 1.1235. I wish it were committed as 2.0 instead. What are my options? All I can think of at the moment is: 1. cvs ad
Why on earth are you fiddling with revision numbers? These numbers had somewhat of a user-visible role in RCS. In CVS, version numbers are an implementation artifact of the repository; just let the s
There isn't any way to move a revision, so you're going to have to create a new revision on the branch and then get rid of the bogus revision on the trunk. What I'd suggest is: 1) Update your working
Hi I would like to set the revision number of a certain file. Instead of going from 1.1 to 1.1+n I would like to state a "base line" and make the file 2.0. I looked in the manual and there it only st
Hi Lukas, Is the revision number important to you? I think the Release-Tag is more important than an particular revision number. Ok. Let's come to an answer to your question: AFAIK there is no way ba
One of my source files has a revision number: 1.277.4.78.2.47.2.32.4.2.2.1.2.12 This is too big (for instance it causes problems in bonsai). It would be nice to set the revision to (say) 2.0 and star
Please post messages to address@hidden. Before you go any further, read the section on revisions in the cvs manual: http://ximbiot.com/cvs/manual/cvs-1.11.21/cvs_4.html#SEC44 CVS version numbers are
Hi, I'm new to this list so please forgive me if I've asked something that has already been asked before(likelihood of this is very high). I've been using CVS on and off over the past few years, but
In general, the individual file revision numbers are, or should be, largely irrelevant; the thing that is really needed are the tags (because in general, the revision of one particular file is meani
OK, not a problem. I had read that but was interested in the best practise. Thanks! Regards Ray Some of the files in my cvs repository have been committed many hundreds of times and we're getting clo
It is possible. However, I urge you to NOT do it. You will likely have more problems down the line should you do so. Please let CVS keep the revisions number private and use tags to help you keep tra
Hi all Some of the files in my cvs repository have been committed many hundreds of times and we're getting close to a major release. Is it possible to increase the major number of the revision histor
As I see it, you have two options: 1) Make your wish come true and live to regret it. 2) Embrace the one true way -- that revision numbers are for CVS's internal use, not for human use -- and live ha
We are doing parallel development with 2 different versions of our code. We have version 2 on a branch and version 3 is on our main trunk. What we want to do is update the revision numbers on the ver