I haven't used svnmerge.py On 20/01/2010 8:04, Dieter Oberkofler wrote:
1) svnmerge.py did generate an informative commit message listing all the logs of the merged revisions is generated in a text file, as a suggestion for a good commit message.
That seems like a workaround for the lack of support by tools. Now that mergeinfo is standard, if you use for instance TSVN, you can (optionally) drill down to the log messages of merged changesets. So the log message of a merge can be to the point: it's a merge. If you want detail of what was merged, let the SVN browser get it for you.
2) When suing svnmerge.py for development branches it had a "merge everything" command (does everything automatically) that also kept track of the directory the branch has been made of. This does no longer seem to be available.
I would certainly like that: the default merge source could be the branch that the working copy's URL is a copy of. So "svn merge" would suffice. But then there are situation where you merge from a different branch, or where the merge source has been renamed (bad practice, I know).
-- Stein
