Hi Kristis
Base: /tags/LIMEPOINT_0_0_0_3_DEV
Target: /tags/LIMEPOINT_0_0_0_4_DEV
Bug list: 700,701 (when entered it will display all affected files)
Then click: "create build"
The operation of merging the files from bugs 701 & 700 will be associated
with a separate automatically generated bug in Mantis is a special
BUILDS -
lets say 800 with automatically
generated references to 700,701 there and extra comments descibing the
build if necessary
the top of /branches/Limepoint_release remains the same
We would need to create a temporary branch to host the changes. Right ?
$ svn copy tags/LIMEPOINT_0_0_0_3_DEV
branches/b_scmbug_merge_on_bug_800_from_LIMEPOINT_0_0_0_3_DEV
# apply the changes of bugs 700 and 701 in this new branch. commit. And
then:
$ svn copy branches/b_scmbug_merge_on_bug_800_from_LIMEPOINT_0_0_0_3_DEV
tags/LIMEPOINT_0_0_0_4_DEV
# and perhaps then remove this temporary branch
$ svn remove --force
branches/b_scmbug_merge_on_bug_800_from_LIMEPOINT_0_0_0_3_DEV
Can do but I don't see any reason why we can't use LIMEPOINT_0_0_0_4_DEV as
the working branch - it doesn't look nice to modify anything in /tags - yes,
but on the other hand looking at files there you can see the history of
changes vs. LIMEPOINT_0_0_0_3_DEV - could be helpful if you introduced some
critical bugs since then or you are trying to figure out why a build
failed...
Best regards
Marek
_______________________________________________
scmbug-users mailing list
[email protected]
http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
