Newsgroups: php.internals,php.qa Path: news.php.net Xref: news.php.net php.internals:54179 php.qa:65885 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 85471 invoked from network); 23 Jul 2011 23:23:30 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Jul 2011 23:23:30 -0000 Authentication-Results: pb1.pair.com smtp.mail=rasmus@lerdorf.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=rasmus@lerdorf.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lerdorf.com from 209.85.210.44 cause and error) X-PHP-List-Original-Sender: rasmus@lerdorf.com X-Host-Fingerprint: 209.85.210.44 mail-pz0-f44.google.com Received: from [209.85.210.44] ([209.85.210.44:54727] helo=mail-pz0-f44.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A5/B4-59700-FE75B2E4 for ; Sat, 23 Jul 2011 19:23:27 -0400 Received: by pzk5 with SMTP id 5so7051388pzk.31 for ; Sat, 23 Jul 2011 16:23:24 -0700 (PDT) Received: by 10.68.47.103 with SMTP id c7mr4796891pbn.277.1311463404688; Sat, 23 Jul 2011 16:23:24 -0700 (PDT) Received: from [192.168.200.5] (c-50-131-46-20.hsd1.ca.comcast.net [50.131.46.20]) by mx.google.com with ESMTPS id k3sm1848371pbj.29.2011.07.23.16.23.22 (version=SSLv3 cipher=OTHER); Sat, 23 Jul 2011 16:23:23 -0700 (PDT) Sender: Rasmus Lerdorf Message-ID: <4E2B57EA.10309@php.net> Date: Sat, 23 Jul 2011 16:23:22 -0700 Organization: PHP Infrastructure team User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:5.0) Gecko/20110627 Thunderbird/5.0 MIME-Version: 1.0 To: Gwynne Raskind CC: PHP QA , internals@lists.php.net References: <4E2AF3D4.9070704@daylessday.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] new gcov.php.net machine is up From: systems@php.net (Rasmus Lerdorf) On 07/23/2011 04:07 PM, Gwynne Raskind wrote: > Here's my question - if I made some smaller commits here and there to > fix warnings in core, would that be accepted? I don't have time to do > sweeping changes, but fixing one file today, a couple the next day, > etc., is within my abilities (including making sure no regressions are > introduced, of course). That's fine if it is done carefully. Note that the code needs to compile on many different platforms, on many different compilers and versions of compilers. -Rasmus