From owner-cvs-all@FreeBSD.ORG Thu Dec 29 16:01:37 2005 Return-Path: X-Original-To: cvs-all@FreeBSD.org Delivered-To: cvs-all@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 81AC816A41F; Thu, 29 Dec 2005 16:01:37 +0000 (GMT) (envelope-from gad@FreeBSD.org) Received: from smtp4.server.rpi.edu (smtp4.server.rpi.edu [128.113.2.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5509643D66; Thu, 29 Dec 2005 16:01:25 +0000 (GMT) (envelope-from gad@FreeBSD.org) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp4.server.rpi.edu (8.13.0/8.13.0) with ESMTP id jBTG1EFK004330; Thu, 29 Dec 2005 11:01:16 -0500 Mime-Version: 1.0 Message-Id: In-Reply-To: <17329.43462.973418.828137@khavrinen.csail.mit.edu> References: <200512222334.jBMNYpxY058133@repoman.freebsd.org> <86ek42s49j.fsf@xps.des.no> <17329.43462.973418.828137@khavrinen.csail.mit.edu> Date: Thu, 29 Dec 2005 11:01:13 -0500 To: Garrett Wollman , des@des.no (Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?= ) From: Garance A Drosehn Content-Type: text/plain; charset="iso-8859-1" ; format="flowed" Content-Transfer-Encoding: quoted-printable X-CanItPRO-Stream: default X-RPI-SA-Score: undef - spam-scanning disabled X-Scanned-By: CanIt (www . canit . ca) on 128.113.2.4 Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/share/zoneinfo - Imported sources X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Dec 2005 16:01:37 -0000 At 3:53 PM -0500 12/27/05, Garrett Wollman wrote: >< >> I wonder if we should make a habit of merging these to security / >> errata branches. > >Not an unreasonable question. The database format has not changed >incompatibly in years, so it's a relatively low-risk thing to merge. >OTOH, updates are sometimes frequent, particularly during the time >of year when governments tend to fiddle their DST adjustments. > >I would suggest only merging updates if there is a significant user >community which is affected by the changes. ... It might be reasonable to merge them when we have something else to put in the security/errata branches. That way people aren't doing buildworld's just for a timezone change, but if they have to do a buildworld anyway then they'll pick up the latest timezone changes. Or something along those lines... I guess the opposing issue is that it might be too much of a hassle to be distracted by MFC's of minor changes when you're anxious to commit some important security fix. -- Garance Alistair Drosehn =3D gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@FreeBSD.org Rensselaer Polytechnic Institute; Troy, NY; USA