From owner-freebsd-questions Tue Nov 27 16:13:47 2001 Delivered-To: freebsd-questions@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 51E2737B41B for ; Tue, 27 Nov 2001 16:13:19 -0800 (PST) Received: from localhost (doug@localhost) by fledge.watson.org (8.11.6/8.11.5) with SMTP id fAS0CqX23742; Tue, 27 Nov 2001 19:12:53 -0500 (EST) (envelope-from doug@safeport.com) X-Authentication-Warning: fledge.watson.org: doug owned process doing -bs Date: Tue, 27 Nov 2001 19:12:51 -0500 (EST) From: doug X-Sender: doug@fledge.watson.org To: Giorgos Keramidas Cc: freebsd-questions@FreeBSD.ORG Subject: Re: cvsup question In-Reply-To: <20011127231220.GB11957@hades.hell.gr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG First I appreciate your response(s). Actually I am not sure it is a bug - just that cvsup does not work as I had thought. It would seems to me that the CVS tag lines (correct term??) in the source were not updated. I just thought I would pursue this issue because I was depending on something that did not work as I had thought. I.e. that the date tag worked on a timestamp (and I guess that all mirrors used ntpd ;) On Wed, 28 Nov 2001, Giorgos Keramidas wrote: > > There should be no timing issue. In my example > > all time are Zulu. > > > > Using the cvsup date tag format: at 2001.11.25.15 (or later) I ran a > > cvsup with no date tag. I observed that the latest mod I picked up was > > 2001.11.24.19+. So to get something that (I thought) would be > > reproducible I ran another cvsup with a tag of 2001.11.25.00.00.00. > > Much earlier than the time of the 2nd cvsup. > > > > I did not get tags anywhere near the boundary times rather I got: > > > > Add delta 1.291.2.22 2001.11.02.16.45.05 > > Add delta 1.74.2.6 2001.11.23.13.13.19 > > Add delta 1.5 99.08.28.01.01.30 > > Add delta 1.5.2.2 2001.07.22.12.40.55 > > Add delta 1.4 99.08.28.01.16.04 > > This seems definitely wrong. Especially the deltas from 99.08.28.*. I assumed this to be human error - I was just surprised they made it in my update. I probably would not have noticed except they were the ONLY changes. Given the number of people, the change rate, and the complexity, I think it all works pretty well. Note none of this caused a problem - just was strange and I was depending on the date tag to do something it (obviously) does not do. > I hope this is not a bug in CVSup that bites you. What version of > CVSup are you running. There was an update this autumn, for a bug > caused by the 1-billionth second. I am using cvsup-16.1d. This does not seems like those kinds of tolerances were involved :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message