On Fri, Jul 17, 2009 at 12:42 AM, Gwynne Raskind <gwy...@darkrainfall.org>wrote:

> On Jul 16, 2009, at 6:19 PM, Jani Taskinen wrote:
>
>> Or just to something more generic like php-commits@ ? The same with
>>> zend-commits?
>>>
>> Only php-commits@ is necessary since there is no separate Zend stuff
>> anymore..?
>>
>
>
> Zend commits are still sent separately. From commit-email.php:
>
>    '|^php/ZendAPI|' => 
> array('zend-engine-cvs@lists.**php.net<zend-engine-...@lists.php.net>',
> 'doc-...@lists.php.net'),
>    '|^php/php-src/Zend|' => 
> array('zend-engine-cvs@lists.**php.net<zend-engine-...@lists.php.net>
> '),
>    '|^php/php-src/TSRM|' => 
> array('zend-engine-cvs@lists.**php.net<zend-engine-...@lists.php.net>
> '),
>
> I'm personally very much in favor of a rename to "php-commits" etc. From
> commit-email.php (again), the list of lists that could be renamed:
>
> php-gtk-...@lists.php.net
> zend-engine-...@lists.php.net
> doc-...@lists.php.net
> pear-...@lists.php.net
> pecl-...@lists.php.net
> gd-...@lists.php.net
> embed-...@lists.php.net
> php-...@lists.php.net
>
> -- Gwynne


more thank 2 years passed, we are planning to move to a DVCS, so maybe we
should re-consider changing at least the zend-engine-cvs@ and php-cvs@ to
zend-engine-commits@and php-commits@ ?

-- 
Ferenc Kovács
@Tyr43l - http://tyrael.hu

Reply via email to