Actually svnmerge generates the svn commit message that is then passed manually to the svn commit message:
svnmerge merge svn commit -F svnmerge-commit-message.txt I can just avoiding to use the svnmerge generated commit message for temporary branch... it may be useful on "stable" branch, when porting from 4.2 to 4.1 or similar, but I agree than when used to sync a branch with the trunk is mainly useless and annying fabrizio 2010/2/19 Grégory Joseph <[email protected]>: > > To users of svnmerge: > > Is there any way to disable the fact that a merge is committed with a > concatenated version of all the log messages of the merged revisions ? Reason > I'm asking is that it makes it quasi-impossible to use the svn commit tabs in > Jira - see for example: > http://jira.magnolia-cms.com/browse/MAGNOLIA-3058?page=com.atlassian.jira.plugin.ext.subversion%3Asubversion-commits-tabpanel > > Alternatively, I could re-configure Jira so that it ignores specific > branches, but that would be a p.i.t.a: it's currently configured to watch all > of the svn repository, and afaik there's no option to "watch all except X", > so I'd have to go and manually add each and every path around the branch we'd > want it to avoid. > > Thoughts ? > > -g > > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- > > ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
