Return-Path: Delivered-To: apmail-httpd-dev-archive@www.apache.org Received: (qmail 16363 invoked from network); 26 Jan 2007 02:25:24 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 26 Jan 2007 02:25:24 -0000 Received: (qmail 93503 invoked by uid 500); 26 Jan 2007 02:25:26 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 93359 invoked by uid 500); 26 Jan 2007 02:25:26 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 93327 invoked by uid 99); 26 Jan 2007 02:25:25 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Jan 2007 18:25:25 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [207.155.248.4] (HELO repulse.cnchost.com) (207.155.248.4) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Jan 2007 18:25:16 -0800 Received: from [192.168.0.21] (c-24-15-193-17.hsd1.il.comcast.net [24.15.193.17]) (as wrowe@rowe-clan.net) by repulse.cnchost.com (ConcentricHost(2.54) Relay) with ESMTP id 2F58D4168; Thu, 25 Jan 2007 21:24:55 -0500 (EST) Message-ID: <45B96655.8040204@rowe-clan.net> Date: Thu, 25 Jan 2007 20:24:21 -0600 From: "William A. Rowe, Jr." User-Agent: Thunderbird 1.5.0.8 (X11/20061107) MIME-Version: 1.0 To: jim@jaguNET.com CC: Jeff Trawick , dev@httpd.apache.org, dev@apr.apache.org Subject: Re: 2007 DST changes, and a "non-issue" statement... References: <200701251343.l0PDhwh23050@devsys.jaguNET.com> In-Reply-To: <200701251343.l0PDhwh23050@devsys.jaguNET.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Jim Jagielski wrote: > Jeff Trawick wrote: >> Is there anything to say other than (for httpd, for example): >> >> Apache httpd and bundled libraries do not maintain their own time zone >> information. Instead, information is retrieved from the operating >> system. Relevant operating system updates must be applied and the web >> server restarted to prevent potential time display problems with >> logging and server-generated reports. >> >> Web applications and third-party modules and libraries used with the >> web server must be investigated separately. >> > > +1 +1 - is this one for the main news page at httpd.apache.org and apr.apache.org? The short and to-the-point style would fit nicely :)