That generates conflicts between the result of the update and the working revision.
Just eliminate the changes made on 1.3 in every version up to this one (1.4 and 1.5 in
my case) and generate 1.6. 1.6 will contain 1.1, 1.2, 1.4 (with no 1.3 changes) and
1.5 (with no 1.3 changes), but 1.4 and
I have made that, and nothing changed at all.
Maybe I did not explain myself well.
A file with 1.1, 1.2, 1.3, 1.4 and 1.5 revisions.
Generate 1.6 tah contains code from 1.1, 1.2, 1.4 and 1.5, I mean to NOT include
changes made in 1.3 revision
Checking out last revision (1.5) and doing cvs
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
A file with 1.1, 1.2, 1.3, 1.4 and 1.5 revisions.
Generate 1.6 tah contains code from 1.1, 1.2, 1.4 and 1.5, I mean to NOT include
Hi All,
Using i.e cvs update -j revision 1.6 -j revision 1.3 file.c, we discard
changes from 1.6 to 1.3. Then, commiting, we get revision 1.7 that is exactly the same
as 1.3. Now, suppose I want to generate a new revision of file.c but containing code
from 1.1 to 1.3 + 1.5 and
