From owner-freebsd-current Thu Dec 31 01:40:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA12032 for freebsd-current-outgoing; Thu, 31 Dec 1998 01:40:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.oeno.com (ns.oeno.com [194.100.99.145]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA12027 for ; Thu, 31 Dec 1998 01:40:06 -0800 (PST) (envelope-from will@ns.oeno.com) Received: (qmail 16325 invoked by uid 1001); 31 Dec 1998 09:39:44 -0000 To: John Polstra Cc: current@FreeBSD.ORG Subject: Re: CVS issues References: From: Ville-Pertti Keinonen Date: 31 Dec 1998 11:39:21 +0200 In-Reply-To: John Polstra's message of "30 Dec 1998 03:44:06 +0200" Message-ID: <86lnjoabw5.fsf@not.oeno.com> Lines: 20 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra writes: > The reason I haven't done it so far is because the mirrors differ > in some of the little-used collections that they carry. They all Are you sure there are no other reasons for not doing it? What happens if you cvsup from a site that has an older version of the tree than you do? Does it do nothing in both repository mode and in checked-out mode? CVS removes changes and gives you an older version if you update from an old repository (at least if you're on the main branch). Which is the right thing for CVS to do because with CVS the only way you should end up with an old repository is if you restore an old backup after you've lost the one that's up-to-date. But if cvsup ever removes changes, a DNS round-robin entry could cause problems that don't occur when always syncing from a specific server. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message