From owner-freebsd-sparc64@FreeBSD.ORG  Fri Feb 20 09:32:33 2004
Return-Path: <owner-freebsd-sparc64@FreeBSD.ORG>
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 075A516A4CE
	for <freebsd-sparc64@freebsd.org>;
	Fri, 20 Feb 2004 09:32:33 -0800 (PST)
Received: from electra.cse.Buffalo.EDU (electra.cse.Buffalo.EDU
	[128.205.32.2])	by mx1.FreeBSD.org (Postfix) with ESMTP id A2DD443D1D
	for <freebsd-sparc64@freebsd.org>;
	Fri, 20 Feb 2004 09:32:32 -0800 (PST)
	(envelope-from kensmith@cse.Buffalo.EDU)
Received: from electra.cse.Buffalo.EDU (kensmith@localhost [127.0.0.1])
	i1KHWWTr001910	for <freebsd-sparc64@freebsd.org>;
	Fri, 20 Feb 2004 12:32:32 -0500 (EST)
Received: (from kensmith@localhost)
	by electra.cse.Buffalo.EDU (8.12.10/8.12.9/Submit) id i1KHWV6l001909
	for freebsd-sparc64@freebsd.org; Fri, 20 Feb 2004 12:32:31 -0500 (EST)
Date: Fri, 20 Feb 2004 12:32:31 -0500
From: Ken Smith <kensmith@cse.Buffalo.EDU>
To: freebsd-sparc64@freebsd.org
Message-ID: <20040220173231.GA1344@electra.cse.Buffalo.EDU>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.1i
Subject: 64btt cvsup?
X-BeenThere: freebsd-sparc64@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting FreeBSD to the Sparc <freebsd-sparc64.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64>,
	<mailto:freebsd-sparc64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-sparc64>
List-Post: <mailto:freebsd-sparc64@freebsd.org>
List-Help: <mailto:freebsd-sparc64-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64>,
	<mailto:freebsd-sparc64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Feb 2004 17:32:33 -0000


Has anyone tried using cvsup on a 64btt system yet?  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.

-- 
						Ken Smith
- From there to here, from here to      |       kensmith@cse.buffalo.edu
  there, funny things are everywhere.   |
                      - Theodore Geisel |