From owner-freebsd-hackers Wed Feb 1 12:00:35 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id MAA05823 for hackers-outgoing; Wed, 1 Feb 1995 12:00:35 -0800 Received: from grunt.grondar.za (grunt.grondar.za [196.7.18.129]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id LAA05806 for ; Wed, 1 Feb 1995 11:59:43 -0800 Received: from localhost (localhost [127.0.0.1]) by grunt.grondar.za (8.6.9/8.6.9) with SMTP id VAA08226; Wed, 1 Feb 1995 21:58:14 +0200 Message-Id: <199502011958.VAA08226@grunt.grondar.za> X-Authentication-Warning: grunt.grondar.za: Host localhost didn't use HELO protocol To: terry@cs.weber.edu (Terry Lambert) cc: phk@ref.tfs.com (Poul-Henning Kamp), hackers@FreeBSD.org Subject: Re: SUP must die, CTM for president !! Date: Wed, 01 Feb 1995 21:58:14 +0200 From: Mark Murray 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. Just one question: what happens when (not if, when) someone misses an update? (trashed message/mailbox, or they go on holiday and the service provider can't handle the mail volume). How does the poor sod get back into step then? A history of these deltas should be kept somewhere, at least for FTP, and possibly for mail retrieval. Some sort of sequencing should also be involved to keep the series accurate. A source tree full of .rej's is a sorry thing. Please don't interpret this as an attempt to kill the idea (which I think is GREAT), I just would like to see it work... -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200