> > - Apply the list of bugs directly onto the base branch. (e.g. merge work > > on a branch into the main trunk). > Nop
I'm saying the tool can be more flexible if we also allow the above. > We use a PHP build generator page in mantis - an interface to perl > scripts - I'm going to write - you specify there: > > 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" I understand the example. It clarifies things a lot. Thanks. The second need I described would also make it possible to: Have a development branch: /branches/b_kpm_experiment_with_fixing_707 I suddenly realize that 707 depends on another fix on bug 708 which was already applied (somewhere, anywhere, it doesn't matter). I could choose to merge this fix into my branch so I can continue work on 707. In this case: Base: /branches/b_kpm_experiment_with_fixing_707 Bug list: 708 and click "create build". Theres no need to specify a "Target", since we imply that we want the bug list changes to be applied directly in Base. It should be possible to implement both capabilities in scmbug_merge, with little effort. What do you think ? In any case, I made considerable progress setting up a scmbug_merge utility that collects the information needed from Mantis. Still have to implement the Bugzilla and RequestTracker backends, but this shouldn't slow you down: http://bugzilla.mkgnu.net/show_bug.cgi?id=545 You could start working on scmbug_merge by modifying src/lib/product/Tools/Merge.pm.in. Or work on the Mantis frontend and I'll work more on the Merge... _______________________________________________ scmbug-users mailing list [email protected] http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
