From owner-cvs-all Sat Jan 23 11:47:52 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA08425 for cvs-all-outgoing; Sat, 23 Jan 1999 11:47:52 -0800 (PST) (envelope-from owner-cvs-all@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA08420 for ; Sat, 23 Jan 1999 11:47:48 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.2/8.9.2/Netplex) with ESMTP id DAA00829; Sun, 24 Jan 1999 03:47:22 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199901231947.DAA00829@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Julian Elischer cc: Nate Williams , Archie Cobbs , cvs-committers@FreeBSD.ORG Subject: Re: Problem with "cvs" on freefall (fwd In-reply-to: Your message of "Sat, 23 Jan 1999 11:05:27 PST." Date: Sun, 24 Jan 1999 03:47:22 +0800 From: Peter Wemm Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk Julian Elischer wrote: > > > On Sat, 23 Jan 1999, Nate Williams wrote: > > > > At work we use CVS exensively, and we've had 'strange' problems using > > CVS 1.10 on repositories built with CVS 1.9 when mixing different > > versions of the cvs binary. (The remote version is different from the > > local version, etc...) > > > > I'm not (yet) convinced that CVS 1.10 is ready for use in mixed > > environments, and since CVS 1.9 is the default FreeBSD version, I > > wouldn't switch. > > We're not suggesting switching just recompiling it from source and > reinstallign it on freefall. The same verrsion that's there already > but there are some bugfixes that have been > committed and it's odd that our own central CVS machine hasn't been > updated. I've held back because jkh was threatening to do a proper freefall update. Where did the binary come from? RELENG_2_2? Whistle's cvs tree? Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message