First thing you want to do is create a non-branch tag based on the -D tag. That tag will indicate the base, or branch point, of the branch. You can use the same tag as the branch, with a suffix such
I am a bit confused about creating a branch off old revision. Basically I checked out a previous revision via "-D" option. Now I want to create a branch and commit the change. I don't want it to merg
Hi, Really short answer: This is normal behavior. Short answer: In general, revision numbers are internally used by cvs. Don't stress about them. In particular, revision 1.1.1.1 (and everything on th
Well, my original mail described the problem I thought. Checkout the same source tree into two sandboxes. Then edit one file in both, making incompatible changes (e.g. append a different line to each
Hi, I've updated from 1.12.9 to 1.12.13 and I'm seeing a *really* major change in behaviour when conflicts happen; a merge conflict is only reported during the merge itself. The conflict marker itsel
If that's the case, then why was the revision number ever exposed in the first place? Is it a legacy of RCS or SCCS - do they not support symbolic tags? So are you saying that "cvs ci -r <revision nu
One way that's kind of in between would be to use "cvs admin -o" to delete the offending revisions, then recommit them, but it'll be a pain to get it right, and it'll only work if the bum revision is
cvs up -j[revision including change you didn't mean to commit] -j[revision before change you didn't mean to commit] filename will merge out the change you meant to get rid of. Sanity check the file,
No, it didn't. No, it isn't. CVS almost certainly did not enter that change request in that form. The number of lines is computed from the number of newline characters in the change text, so there we
Yes, thanks for the idea, -- it seems that was indeed the case, -- I've tried to import 2 times a test project containing single file (changing it between first and second import), and got similar re
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
The basic problem is that you will may very well find out that CVS is making assumptions about revision numbers fitting some 1.x format, as revision numbers starting with anything other than `1.' are
Heh, I think you misunderstood my second message. I meant that we wanted to make the change for cosmetic reasons, not that it WAS a cosmetic change. After reading on how the branches are created, I
Hi Fabian & all, It does not work. It does do nothing!. My idea is generate a new revision but deleting changes made in a very old revision... Thanks Rolo
The rinfo program can display a list of version numbers between two given versions. It accomodates removed revisions, branches, and magic branches, which complicate the computation. And its output is
I am trying to customize some change reports we generate using the CVS tools available in Ant - which basically means I can execute any arbitrary CVS command line. The reports can already determine w
hello, I want to set revision of module in cvs as 1.2.0.1 by cvs import -b command. But now if somebody checkout this module and change some thing in this module and then commit. So i don't want that
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
Personally I would just hack at the CVS/Entries file in your sandbox and change the revision to 1.2 for foo.bar it will let you commit then.... You can all throw tomatoes at me now, I'm a naught than
That will only happen if you manually force the revision number in a commit (I forget if this is even an option in cvs - the only time I've ever actually done it is with RCS, which does allow specify