|Version Management with CVS - the CVS manual|
by Per Cederqvist et al.
Paperback (6"x9"), 216 pages, 8 figures
RRP £19.95 ($29.95)
5.7 Merging from a branch several times
Continuing our example, the revision tree now looks like this: where the dashed line represents the merge from the ‘R1fix’ branch to the main trunk, as just discussed.
Now suppose that development continues on the
and then you want to merge those new changes onto the
main trunk. If you just use the
cvs update -j
R1fix m.c command again, CVS will attempt to
merge again the changes which you have already merged,
which can have undesirable side effects.
So instead you need to specify that you only want to merge the changes on the branch which have not yet been merged into the trunk. To do that you specify two ‘-j’ options, and CVS merges the changes from the first revision to the second revision. For example, in this case the simplest way would be
# Merge changes from 220.127.116.11 to the head of the R1fix branch $ cvs update -j 18.104.22.168 -j R1fix m.c
The problem with this is that you need to specify the 22.214.171.124 revision manually. A slightly better approach might be to use the date the last merge was done:
$ cvs update -j R1fix:yesterday -j R1fix m.c
Better yet, tag the R1fix branch after every merge into the trunk, and then use that tag for subsequent merges:
$ cvs update -j merged_from_R1fix_to_trunk -j R1fix m.c
|ISBN 0954161718||Version Management with CVS - the CVS manual||See the print edition|