Re: Re: svn: /php/php-src/branches/PHP_5_3/ext/gd/ libgd/gdft.c tests/bug48555.phpt tests/bug48732.phpt tests/bug48801.phpt

From: Date: Tue, 28 Jul 2009 16:43:10 +0000
Subject: Re: Re: svn: /php/php-src/branches/PHP_5_3/ext/gd/ libgd/gdft.c tests/bug48555.phpt tests/bug48732.phpt tests/bug48801.phpt
References: 1 2 3 4 5  Groups: php.internals 
Request: Send a blank email to internals+get-45124@lists.php.net to get a copy of this message
Gwynne Raskind 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.
It's only sparse checkout that works for us. --Jani

« previous php.internals (#45124) next »