Date: Tue, 01 Dec 1998 01:33:32 -0700 From: Warner Losh <imp@village.org> To: obrien@NUXI.com Cc: Archie Cobbs <archie@whistle.com>, committers@FreeBSD.ORG Subject: Re: ports tree FROZEN now Message-ID: <199812010833.BAA01703@harmony.village.org> In-Reply-To: Your message of "Tue, 01 Dec 1998 00:04:19 PST." <19981201000419.B2859@nuxi.com> References: <19981201000419.B2859@nuxi.com> <199812010631.RAA03547@cimlogic.com.au> <199812010732.XAA25873@bubba.whistle.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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. Comments? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199812010833.BAA01703>