On 24.01.2009, at 17:40, Ilia Alshanetsky wrote:
I think our bug current tracker is pretty good and most importantly
makes it easy to report and update bugs which is conducive to more
issues being reported. Often extra features of bug trackers make
them overly complex to use and people
hi everyone,
On Sat, Jan 24, 2009 at 11:40:08AM -0500, Ilia Alshanetsky wrote:
I think our bug current tracker is pretty good and most importantly
makes it easy to report and update bugs which is conducive to more
issues being reported. Often extra features of bug trackers make them
In that case why wasn't this pointed out last year, and I could of done
something more useful with my GSoC time last year..
On Sun, 25 Jan 2009 15:05:37 +0100, sean finney sean...@debian.org wrote:
hi everyone,
On Sat, Jan 24, 2009 at 11:40:08AM -0500, Ilia Alshanetsky wrote:
I think our
Stop top-posting.
On Sun, Jan 25, 2009 at 15:17, ba...@barrycarlyon.co.uk wrote:
In that case why wasn't this pointed out last year, and I could of done
something more useful with my GSoC time last year..
I did:
Hi,
I think that there needs to be more feedback from the community on how
projects are going and the way they should go. This might help to curb some
of the problems being discussed where there was a gap between the project
and what the community wants. Feedback would also help the student know
On 25.01.2009, at 16:17, Graham Kelly wrote:
Lastly, I really think all the PHP GSoC projects should be hosted in
PHP's
CVS under a central location (maybe something like
/repository/gsoc/2009/projectname/). It was very hard at times to
find the
work done for other projects.
Actually
On 24.01.2009, at 19:19, Guilherme Blanco wrote:
Hi Oskar,
Yes, you can use a plain array too.
I was just giving you a normal approach (ArrayAccess inherited class)
because you may want a special behavior under it too.
Forget SplObjectStorage docs they're outdated read the
source!
On Sun, Jan 25, 2009 at 02:17:31PM +, ba...@barrycarlyon.co.uk wrote:
In that case why wasn't this pointed out last year, and I could of done
something more useful with my GSoC time last year..
http://markmail.org/message/daf4zi5dfktv7jjt
sean
signature.asc
Description:
Am 25.01.2009 um 14:29 schrieb Lukas Kahwe Smith:
On 24.01.2009, at 17:40, Ilia Alshanetsky wrote:
I think our bug current tracker is pretty good and most importantly
makes it easy to report and update bugs which is conducive to more
issues being reported. Often extra features of bug
On 25 Jan 2009, at 16:12, David Zülke wrote:
Am 25.01.2009 um 14:29 schrieb Lukas Kahwe Smith:
On 24.01.2009, at 17:40, Ilia Alshanetsky wrote:
I think our bug current tracker is pretty good and most
importantly makes it easy to report and update bugs which is
conducive to more issues
On 25 Jan 2009, at 15:22, Lukas Kahwe Smith wrote:
On 25.01.2009, at 16:17, Graham Kelly wrote:
Lastly, I really think all the PHP GSoC projects should be hosted
in PHP's
CVS under a central location (maybe something like
/repository/gsoc/2009/projectname/). It was very hard at times to
On Sun, Jan 25, 2009 at 5:22 PM, Scott MacVicar sc...@macvicar.net wrote:
On 25 Jan 2009, at 15:22, Lukas Kahwe Smith wrote:
On 25.01.2009, at 16:17, Graham Kelly wrote:
Lastly, I really think all the PHP GSoC projects should be hosted in
PHP's
CVS under a central location (maybe something
Sean,
You make some very good points and I'll be the first to agree there is
definitely a room to improve the existing bug-tracker, in particular
its integration with the repository commits, but I do not think it
needs a fundamental rewrite. From what I can see most (I think its
all, but
Hello all, and sorry for the massive cross-posting :)
As of now we have a list dedicated to Google Summer Of Code[1] discussions.
It is our hope that everyone who are interested in PHP and GSOC
subscribe[2] to the list and participate in the discussions, or just
lurk and follow the fun.
Among
Greetings,
I recently upgraded to the latest PHP 5.3 snapshot and I found the following
SoapClient bug:
?php
ini_set(soap.wsdl_cache_enabled, 0);
new SoapClient(http://localhost/ws/catalog?wsdl;);
?
Fatal error: Uncaught SoapFault exception: [WSDL] SOAP-ERROR: Parsing WSDL:
Couldn't load
On Sun, Jan 25, 2009 at 22:43, Giovanni Giacobbi giova...@giacobbi.net wrote:
The problem turned out to be an invalid interpretation of the HTTP/1.1
protocol with Transfer-Encoding: chunked by the HTTP stream context, which
caused get_sdl() to parse a WSDL including the chunk tags (hex
Hello,
On Sun, Jan 25, 2009 at 4:24 PM, Lukas Kahwe Smith m...@pooteeweet.org wrote:
On 24.01.2009, at 19:19, Guilherme Blanco wrote:
Hi Oskar,
Yes, you can use a plain array too.
I was just giving you a normal approach (ArrayAccess inherited class)
because you may want a special behavior
Hannes Magnusson wrote:
On Sun, Jan 25, 2009 at 22:43, Giovanni Giacobbi giova...@giacobbi.net
wrote:
The problem turned out to be an invalid interpretation of the HTTP/1.1
protocol with Transfer-Encoding: chunked by the HTTP stream context, which
caused get_sdl() to parse a WSDL including
Hi,
the recent email about pg_get_socket reminded me that PDO:PgSQL doesn't
have notify support. Here's a small patch and a phpt that add support
for the LISTEN/NOTIFY mechanism using PDO. The PDO::pgsqlGetNotify
method only returns an assoc array, but it could be easily modified to
mimic the
On Sun, Jan 25, 2009 at 11:06:51PM +0100, Hannes Magnusson wrote:
?php
$opts = array('http' = array('method' = GET, 'header' =
Accept-language: en\r\nConnection: close\r\n));
$context = stream_context_create($opts);
stream_context_set_option($context, http, protocol_version, 1.1);
20 matches
Mail list logo
