Re: Re: cvs: php-src /ext/mysql php_mysql.c /ext/mysqli mysqli.c /ext/mysqlnd mysqlnd.c mysqlnd_palloc.c mysqlnd_ps.c mysqlnd_wireprotocol.c
| From: | Andrey Hristov | Date: | Tue, 15 Jul 2008 18:18:00 +0000 |
| Subject: | Re: Re: cvs: php-src /ext/mysql php_mysql.c /ext/mysqli mysqli.c /ext/mysqlnd mysqlnd.c mysqlnd_palloc.c mysqlnd_ps.c mysqlnd_wireprotocol.c | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-38979@lists.php.net to get a copy of this message | ||
Pierre Joye wrote:
On Tue, Jul 15, 2008 at 7:47 PM, Andrey Hristov <php@hristov.com> wrote:What do you mean? That every addition should be committed daily in small chunks? A feature is a feature, it's integral. Because CVS hinders the easiness of work to commit several changeset from a local repository to the main one, even just announcing the patches, without even committing them to the main repository, shows that you will support some distributed RCS to be used for PHP. CVS is ok for 1-2 people touching the same code but not for cooperative development without much of external communication. Best, AndreyPierre Joye wrote:That's not what I meant, by daily jobs I meant daily commits (be fix or adding a feature).The Zend guys are paid to develop and fix Zend. The Oracle guys support oci8 Google gives Marcus time to do open-source work. The company you work for supports you in your work on the PHP, because then they get first-class PHP developer in house. So, I am quite sure people are paid to do the work, one way or another.I have no clue if Andrey has combined several fixes in one commit. At this point I have to rely on him choosing a proper granularity for a commit. Too large commits can always happen. You can work for a month in your local CVS copy and commit 100k at one - no difference.Except that nobody does that for daily jobs and fixes.