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: | Takeshi Abe | Date: | Mon, 27 Jul 2009 23:38:28 +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 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-45110@lists.php.net to get a copy of this message | ||
Hi,
On Mon, 27 Jul 2009 18:44:20 -0400, Gwynne Raskind <gwynne@darkrainfall.org> wrote:
>> 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.
Yes, I agree svn merge will work well.
IIRC, though, it involves a leading commit for trunk (usually, or sometimes for
some branch whatever) and then merged ones for other branches.
Are such sereval commits OK?
Cheers,
-- Takeshi Abe