From owner-freebsd-current  Sun Aug 11 16:04:36 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id QAA17855
          for current-outgoing; Sun, 11 Aug 1996 16:04:36 -0700 (PDT)
Received: from ctasim.com (ctasim.com [206.6.123.1])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id QAA17850
          for <freebsd-current@FreeBSD.ORG>; Sun, 11 Aug 1996 16:04:33 -0700 (PDT)
Received: by deepthought.ctasim.com (940816.SGI.8.6.9/920502.SGI.AUTO)
	 id RAA02075; Sun, 11 Aug 1996 17:00:50 -0600
From: jon@ctasim.com ("Jon Doran" )
Message-Id: <9608111700.ZM2073@deepthought.ctasim.com>
Date: Sun, 11 Aug 1996 17:00:45 -0600
In-Reply-To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
        "Re: Irrelevant comments on cvsup" (Aug 11,  3:19pm)
References: <10562.839801989@time.cdrom.com>
X-Mailer: Z-Mail (3.2.0 26oct94 MediaMail)
To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Subject: Re: Irrelevant comments on cvsup
Cc: John Polstra <jdp@polstra.com>, freebsd-current@FreeBSD.ORG
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Aug 11,  3:19pm, Jordan K. Hubbard wrote:
>
> 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
>-- End of excerpt from Jordan K. Hubbard

Not if indent was ran on both with the same setup file.  We do this at our
company without incident.  Also, there are a fair number of people who will
work with any editable/readable version of the source, so once the source
tree is cleaned up it stays that way.

I'm not suggesting this for FreeBSD, just using it to illustrate the type
of actions that people may wish to perform on checkin/checkout.

Another one is rebuilding tags :-)  I do this via cron in the middle of the
night, but would love to have things updated incrementaly.

Knowing when/what things change is important, but there are ways to make people
work hard to circumvent the system.  In general, timestamps will change
someplace.  If someone dumps code into the tree without using RCS, and then
changes the timestamps back, there are other ways of dealing with them.  A
blunt object over the head should work well.

Jon Doran