On 1/29/2013 6:54 PM, Stas Malyshev wrote:
Hi!
I think having stuff on the wiki is nice, but for things related to the
code - e.g., APIs, builds descriptions, etc. - they should stay in the
code. They are easier to find there and easier to keep up-to-date, and
also ensure they have the content r
Hi!
I think having stuff on the wiki is nice, but for things related to the
code - e.g., APIs, builds descriptions, etc. - they should stay in the
code. They are easier to find there and easier to keep up-to-date, and
also ensure they have the content relevant to specific version. We could
have a
On Tue, 29 Jan 2013, Ferenc Kovacs wrote:
> I think some of the README files currently present in the php-src repo
> would be better kept in the wiki and some of them are already
> duplicated/made redundant by our existing wiki pages.
Please leave them in the source tree. They describe how APIs
On Tue, Jan 29, 2013 at 2:31 PM, Ferenc Kovacs wrote:
>
>
>
> On Tue, Jan 29, 2013 at 2:17 PM, Clint Priest wrote:
>
>>
>> On 1/29/2013 5:21 AM, Ferenc Kovacs wrote:
>>
>> Hi,
>>
>> I think some of the README files currently present in the php-src repo
>> would be better kept in the wiki and som
Am 29.01.2013 12:21, schrieb Ferenc Kovacs:
> what do you think about this?
+1
--
Sebastian BergmannCo-Founder and Principal Consultant
http://sebastian-bergmann.de/ http://thePHP.cc/
--
PHP Internals - PHP Runtime Development Mailing List
To unsu
Hi,
I think some of the README files currently present in the php-src repo
would be better kept in the wiki and some of them are already
duplicated/made redundant by our existing wiki pages.
- README.MAILINGLIST_RULES -> this should be in the wiki or on
php.netsomewhere, this doesn't belong to
