From owner-cvs-all Tue Dec 1 11:12:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA04438 for cvs-all-outgoing; Tue, 1 Dec 1998 11:12:58 -0800 (PST) (envelope-from owner-cvs-all@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA04424 for ; Tue, 1 Dec 1998 11:12:55 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id LAA18352; Tue, 1 Dec 1998 11:11:04 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma018348; Tue, 1 Dec 98 11:10:47 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id LAA27894; Tue, 1 Dec 1998 11:10:47 -0800 (PST) From: Archie Cobbs Message-Id: <199812011910.LAA27894@bubba.whistle.com> Subject: Re: ports tree FROZEN now In-Reply-To: <199812010833.BAA01703@harmony.village.org> from Warner Losh at "Dec 1, 98 01:33:32 am" To: imp@village.org (Warner Losh) Date: Tue, 1 Dec 1998 11:10:47 -0800 (PST) Cc: obrien@NUXI.com, committers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk Warner Losh writes: > One suggestion that I've not seen yet: > > Make a .cvs-lock file, check it in. CVS would then look for this file > in ., then .., etc up to the root of the tree when you want to commit > something. If the file is present, then it will splat its contents to > stdout and ask "In light of the above, are you really sure you want to > commit?" For the ports freeze, the file would look like: > > WE ARE IN PORTS FREEZE NOW. ALL CHANGES MUST BE APPROVED BY > ASAMI-SAN. COMMIT PRIVS WILL BE REVOKED IF YOU COMMIT NOW. > > In light of the above, are you really sure you want to commit? > > I don't know about you, but I'd think twice about answering yes :-) > > Basically, it is an advisory lock rather than a strict lock. cvs > commit has a -f option, which could be used by the release engineer to > bypass this message (or an environment variable CVS_RELEASE_ENGINEER > that would bypass this). > > Sure, I can still check stuff into the tree, but at least I'd get a > warning, or I'd get rained on for aughting to have known better if I'm > silly enough to have CVS_RELEASE_ENGINEER in my environment and not > pay extra special close attention to -current or whatever. This system seems to make *a lot* more sense than: - Satoshi broadcasts an email which, because the world is not perfect, a couple of people miss or forget or whatever, and then - Several people check-in code when they're not supposed to - Satoshi has to yell at all of them - Same people read the email with Satoshi yeling at them - Same people un-check-in they code they checked-in before - Satoshi has to make sure the check-in's didn't screw anything up in the mean time Which is what we witnessed in the past few days.. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message