Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:27147 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 35496 invoked by uid 1010); 20 Dec 2006 16:06:47 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 35481 invoked from network); 20 Dec 2006 16:06:47 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 20 Dec 2006 16:06:47 -0000 Authentication-Results: pb1.pair.com smtp.mail=apache@osu1.php.net; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=zoe@uk.ibm.com; sender-id=softfail Received-SPF: error (pb1.pair.com: domain osu1.php.net from 140.211.166.39 cause and error) X-PHP-List-Original-Sender: apache@osu1.php.net X-Host-Fingerprint: 140.211.166.39 osu1.php.net Linux 2.4/2.6 Received: from [140.211.166.39] ([140.211.166.39:60383] helo=osu1.php.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id EA/1C-55975-47F59854 for ; Wed, 20 Dec 2006 11:06:12 -0500 X-Host-Fingerprint: 127.0.0.1 unknown Received: from [127.0.0.1] ([127.0.0.1:60458] helo=osu1.php.net) by osu1.php.net (ecelerity 2.1.1.11-rc1 r(13363/13364M)) with ESMTP id F2/F1-19413-51F59854 for ; Wed, 20 Dec 2006 08:04:37 -0800 Received: (from apache@localhost) by osu1.php.net (8.12.11/8.12.11/Submit) id kBKG4YDQ022191; Wed, 20 Dec 2006 08:04:34 -0800 Date: Wed, 20 Dec 2006 08:04:34 -0800 To: internals@lists.php.net Message-ID: Subject: CVS Account Request: zoe From: zoe@uk.ibm.com ("Zoe Slattery") I've been looking at the php tests and would like to be able to contribute more tests for basic PHP functions to help increase the test coverage and prevent regressions when code is changed. I don't know how granular the CVS access controls are so am not sure what is possible. I've been working from gcov.phpt.net and looking for gaps in coverage - so far just /ext/standard/levenshtein.c and ext/standard/assert.c. It would also be helpful if I could maintain update the documentation if there is agreement that something is working as designed but not as documented.This was discussed briefly with Andi G and Zeev who suggested applying.