Moriyoshi Koizumi wrote: > Incorporating the changes and merges across the branches into one > commit under a sparse-layouted local copy doesn't do the book-keeping > against svn:mergeinfo. That's why I suppose it is not a good idea.
I don't think a merge will work the way we use branches though. Once you merge you aren't supposed to keep making changes on the branch. merge is good for when you create a branch to work on some larger feature and when it is ready you merge it into trunk and continue working on it in trunk. -Rasmus -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
