Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:48551 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 95183 invoked from network); 28 May 2010 13:22:23 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 28 May 2010 13:22:23 -0000 Authentication-Results: pb1.pair.com smtp.mail=johannes@schlueters.de; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=johannes@schlueters.de; sender-id=unknown Received-SPF: error (pb1.pair.com: domain schlueters.de from 217.114.211.66 cause and error) X-PHP-List-Original-Sender: johannes@schlueters.de X-Host-Fingerprint: 217.114.211.66 unknown Solaris 10 (beta) Received: from [217.114.211.66] ([217.114.211.66:43978] helo=schlueters.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id FE/2C-09614-383CFFB4 for ; Fri, 28 May 2010 09:22:12 -0400 Received: from localhost (ka.local [127.0.0.1]) by schlueters.de (Postfix) with SMTP id 0078C24F82 for ; Fri, 28 May 2010 15:22:09 +0200 (CEST) Received: from [192.168.1.33] (ppp-93-104-121-225.dynamic.mnet-online.de [93.104.121.225]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by schlueters.de (Postfix) with ESMTPSA id A5F0C24F81 for ; Fri, 28 May 2010 15:22:08 +0200 (CEST) To: PHP internals list Content-Type: text/plain; charset="UTF-8" Date: Fri, 28 May 2010 15:22:02 +0200 Message-ID: <1275052922.23351.292.camel@guybrush> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: ChangeLog From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=) Hey, I know type hints are more fun to discuss but anyways: In trunk ChangeLog lists entries up till 2005 (when 5.2 was branched of, from which 5.3 was branched from which the current trunk was branched of) In the old trunk the file lasts until 2009-07-08 (when we switched from CVS to svn) Is anybody using this file? If this is thee case could somebody then make sure it's being updated (and maybe take care of ChangeLog-200[6-9].gz being created) else I'd suggest dropping them. An outdated file might be confusing for users expecting content like we have in the NEWS file there. johannes