From owner-freebsd-current Sun Aug 11 15:21:28 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA16070 for current-outgoing; Sun, 11 Aug 1996 15:21:28 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA16065 for ; Sun, 11 Aug 1996 15:21:26 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id PAA10564; Sun, 11 Aug 1996 15:19:50 -0700 (PDT) To: jon@ctasim.com ("Jon Doran" ) cc: John Polstra , freebsd-current@FreeBSD.ORG Subject: Re: Irrelevant comments on cvsup In-reply-to: Your message of "Sun, 11 Aug 1996 15:49:54 MDT." <9608111549.ZM1725@deepthought.ctasim.com> Date: Sun, 11 Aug 1996 15:19:49 -0700 Message-ID: <10562.839801989@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > You can either generate the checksums during off hours from a cron job, or > build them up as things change. As you pointed out, there are always people "Knowing when things change" is, of course, the art here. :-) > First, consider people who dump things into the tree via RCS or CVS. Lets > use RCS, since its a lower common denominator. It would be useful to place > hooks in RCS to run filters at various stages of the ci and co process. For > example, a site may have standards on the format of code in the tree, so part > of the ci process might involve running indent on all code to convert it into > the standard format. Part of the co process might involve running indent Perhaps you've just picked a poor example here, but that seems like a pretty whacked-out idea to me. If you checked in code for, say, vi and this auto-indenter ran on it, then Keith sent you another version of vi and you wanted to see what had changed between the two versions, you'd be totally screwed. I dunno, I'd say a feature like this would be like a double-edged sword with no hilt. Jordan