From owner-freebsd-sparc64@FreeBSD.ORG Fri Feb 20 10:06:59 2004 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C289C16A4CE for ; Fri, 20 Feb 2004 10:06:59 -0800 (PST) Received: from mail.seekingfire.com (coyote.seekingfire.com [24.72.10.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC88D43D1D for ; Fri, 20 Feb 2004 10:06:59 -0800 (PST) (envelope-from tillman@seekingfire.com) Received: by mail.seekingfire.com (Postfix, from userid 500) id 66D3D299; Fri, 20 Feb 2004 12:06:59 -0600 (CST) Date: Fri, 20 Feb 2004 12:06:59 -0600 From: Tillman Hodgson To: freebsd-sparc64@freebsd.org Message-ID: <20040220180659.GL68388@seekingfire.com> References: <20040220173231.GA1344@electra.cse.Buffalo.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040220173231.GA1344@electra.cse.Buffalo.EDU> X-Habeas-SWE-1: winter into spring X-Habeas-SWE-2: brightly anticipated X-Habeas-SWE-3: like Habeas SWE (tm) X-Habeas-SWE-4: Copyright 2002 Habeas (tm) X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this X-Habeas-SWE-6: email in exchange for a license for this Habeas X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this X-Habeas-SWE-9: mark in spam to . X-GPG-Key-ID: 828AFC7B X-GPG-Fingerprint: 5584 14BA C9EB 1524 0E68 F543 0F0A 7FBC 828A FC7B X-GPG-Key: http://www.seekingfire.com/gpg_key.asc X-Urban-Legend: There is lots of hidden information in headers User-Agent: Mutt/1.5.6i Subject: Re: 64btt cvsup? X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Feb 2004 18:06:59 -0000 On Fri, Feb 20, 2004 at 12:32:31PM -0500, Ken Smith wrote: > > Has anyone tried using cvsup on a 64btt system yet? I'm trying it now for /usr/ports. > I'm getting odd results on a system being set up as a cvsup mirror - > it seems to think it needs to touch (timestamp correction) every file > in the repo but there is no visible change to the timestamp on the > files themselves. I haven't tried running cvsup to update /usr/src or > /usr/ports yet, I was planning to use raw cvs and the local repo to > update the one machine I've cut over to 64btt so far, at least until > I've got the 64btt snapshot built. > > If others have used cvsup and not had a problem I'll just ignore it, > if others are seeing similar things I could report it to jdp. It seems to be working file as far as correctly matching and pulling deltas. I haven't done the INDEX building stage yet, though. -T -- Page 38: Be sure that, in the excitement of creating a totally rad password, you resist the temptation to tell someone just to show off how smart you are. - Harley Hahn, _The Unix Companion_