From owner-freebsd-hackers Wed Feb 1 11:03:14 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id LAA02171 for hackers-outgoing; Wed, 1 Feb 1995 11:03:14 -0800 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id LAA02161 for ; Wed, 1 Feb 1995 11:03:12 -0800 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA06793; Wed, 1 Feb 95 09:15:15 MST From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9502011615.AA06793@cs.weber.edu> Subject: Re: SUP must die, CTM for president !! To: phk@ref.tfs.com (Poul-Henning Kamp) Date: Wed, 1 Feb 95 9:15:14 MST Cc: hackers@FreeBSD.org In-Reply-To: <199502010755.XAA19507@ref.tfs.com> from "Poul-Henning Kamp" at Jan 31, 95 11:55:46 pm X-Mailer: ELM [version 2.4dev PL52] Sender: hackers-owner@FreeBSD.org Precedence: bulk > We set up a machine, (thud probably) to run a shell script X times per day > (X in [1..4]) which does a "make cleandist ; make obj ; make all" and if > that succeeds it produces a CTM delta, which gets put in the public > area on ftp.freebsd.org automatically and emailed to the ctm-src-cur > mailing list at the same time. I suggested something similar to this, but with a slightly more elaborate protocol to keep crap from getting into the CVS treee in the first place and to allow multiple reader/writer use over NFS. Maybe you can add automatic mailing to the committer from the CVS log of the last writer on the failed file? This would go 2/3's of the way to what I suggested without requiring the typing of a command before and after commit sequences. Of course, the "several times a day" is clearly a reference to the fact that there is not a reader lock, so you can't be guaranteed a consistent state when you checkout for the build. Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers.