Date: Thu, 29 Dec 2005 11:01:13 -0500 From: Garance A Drosehn <gad@FreeBSD.org> To: Garrett Wollman <wollman@csail.mit.edu>, des@des.no (Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?= ) Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/share/zoneinfo - Imported sources Message-ID: <p06230906bfd9b681b6a3@[128.113.24.47]> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
At 3:53 PM -0500 12/27/05, Garrett Wollman wrote: ><<On Sat, 24 Dec 2005, des@des.no (Dag-Erling Sm=F8rgrav) said: > >> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p06230906bfd9b681b6a3>