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.
Moriyoshi On Tue, Jul 28, 2009 at 7:44 AM, Gwynne Raskind<gwy...@darkrainfall.org> wrote: > On Jul 27, 2009, at 6:31 PM, Takeshi Abe wrote: >>> >>> Just to be sure, is there any consensus on this? I thought I should >>> use svn merge. >> >> README.SVN-RULES says >> >> 1. All changes should first go to trunk and then get merged from trunk >> (aka MFH'ed) to all other relevant branches. >> >> which I've been following so far. > > That document is outdated. It's now (strongly) preferred that you use one of > the various methods for multi-branch commits available in SVN, using merge > or a sparse checkout. > > -- Gwynne > > -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
