I'd say that its the trac plugin. Its picking up the fact that the bugs were closed on the branch and when it sees the comment again then it tries to close the bug again. Could the trac plugin be modified to ignore comments when the string 'svnmerge' is in the log message? Interesting it didn't spam http://svn.boost.org/trac/boost/changeset/45019though so trac may be doing something more complex.. Of course this can be worked around by users if it becomes a problem by removing the bug numbers from the log messages, although I'd admit its not a convenient fix and one that'd be easy to forget given the workflow for svnmerge.py James 2008/5/6 Rene Rivera <grafikrobot@gmail.com>:
Having an svnmerge command like in this case <http://svn.boost.org/trac/boost/changeset/45029> spew commentary all over existing trac items like this one <http://svn.boost.org/trac/boost/ticket/1889>, just seems like a really bad thing.
Is this yet another reason not to use svnmerge? Or is it operator (not to pick on Eric) error that can be averted in the future? Or could it be the trac comment plugin causing this, and svnmerge is blameless?
-- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org (msn) - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim,yahoo,skype,efnet,gmail _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost