Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:31384
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 66.249.92.172 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:user-agent:mime-version:to:subject:content-type:content-transfer-encoding;
        b=BFaPM5Q4T8ohSKFf6INqa0GIkrPyPolkStdqGfZYLZ8e3fFAupo5zE9XYtv9zGoTBON7qu/NSgyxXCcyE90y23kxLC8naL7NHNNHMvhYEu6bbszsVR663Qf1Lc5YLtRiBQVZCKADWhypMhig52VqIrhVkFKSrz1cplEWYFnRW4E=
Message-ID: <46B24C2F.4000505@gmail.com>
Date: Thu, 02 Aug 2007 23:27:11 +0200
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To:  internals@lists.php.net
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Regarding the ext/curl extension
From: giunta.gaetano@gmail.com (Gaetano Giunta)

> But pushing the PHP docs (as Steph suggested later) to your site will
> only bring you more questions about php's CURL binding. It sounds like
> a bad idea :)

The fact is that Daniel does a wonderful job giving out plenty of advice to php/curl help seekers not just on its website (I'd go as far as saying that the php man pages are better for that), but especially on the curl-and-php mailing list.
That's where a lot of the n00bs end up asking questions.
Sometimes Daniel does not have the definitive answer, as the question really depends on the php 'wrapper', and people get pissed off.
The easy solution: move the mailing list over to php.net, and/or subscribe to it all of the committers to /ext/curl (and yes, I have been subscribed to the mailing list, but had overall more questions than answers...)