From owner-freebsd-current  Sat Aug 19 12:36:24 1995
Return-Path: current-owner
Received: (from majordom@localhost)
          by freefall.FreeBSD.org (8.6.11/8.6.6) id MAA26311
          for current-outgoing; Sat, 19 Aug 1995 12:36:24 -0700
Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241])
          by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id MAA26305
          for <FreeBSD-current@freefall.FreeBSD.org>; Sat, 19 Aug 1995 12:36:22 -0700
Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id MAA00275; Sat, 19 Aug 1995 12:35:19 -0700
From: "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com>
Message-Id: <199508191935.MAA00275@gndrsh.aac.dev.com>
Subject: Re: sup/cvs interactions?
To: rich@lamprey.utmb.edu
Date: Sat, 19 Aug 1995 12:35:18 -0700 (PDT)
Cc: FreeBSD-current@freefall.FreeBSD.org
In-Reply-To: <199508191859.NAA09390@id.slip.bcm.tmc.edu> from "Rich Murphey" at Aug 19, 95 01:59:25 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 1341      
Sender: current-owner@FreeBSD.org
Precedence: bulk

> 
> 
> Is it possible that the time stamp on a given file in
> /usr/src could ever move backward (become older)?  Could CVS
> do this when you revert changes?

No, cvs does not do that.  On an initial cvs co operation it sets the
date of the file to the time of the last commit.

On all supsequent cvs update operations it sets the time on the file
to the current date and time (this is so that make does not get confused.).

> Sup ignores files that are older on the server than on the
> client, so it wouldn't pick up this kind of change.

This depends on sup options.

> I'm seeing this once in a while.. Rich

Do you have ``old'' in your supfile lines?  Or do you run sup -o?

       -o	Sup will normally  only  upgrade  files  that  have
		changed  on  the  repository since the last time an
		upgrade was performed. That is, if the file in  the
		repository  is  newer  than  the date stored in the
		when file on the client.  The -o flag, or  the  old
		supfile  option,  will cause sup to check all files
		in the collection for changes instead of  just  the
		new ones.

I run without the old option, but on occasion do a sup -o just to
make sure things are staying in sync.


-- 
Rod Grimes                                      rgrimes@gndrsh.aac.dev.com
Accurate Automation Company                 Reliable computers for FreeBSD