From owner-freebsd-current@FreeBSD.ORG Wed Aug 18 19:06:46 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D792F16A4CE for ; Wed, 18 Aug 2004 19:06:46 +0000 (GMT) Received: from sirius.firepipe.net (sirius.firepipe.net [69.13.116.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8FA3B43D67 for ; Wed, 18 Aug 2004 19:06:46 +0000 (GMT) (envelope-from will@csociety.org) Received: by sirius.firepipe.net (Postfix, from userid 1000) id 3793A180F7; Wed, 18 Aug 2004 14:06:46 -0500 (EST) Date: Wed, 18 Aug 2004 14:06:46 -0500 From: Will Andrews To: current@FreeBSD.org Message-ID: <20040818190646.GF90227@sirius.firepipe.net> Mail-Followup-To: current@FreeBSD.org References: <1092844084.705.7.camel@localhost.kitchenlab.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="mR8QP4gmHujQHb1c" Content-Disposition: inline In-Reply-To: <1092844084.705.7.camel@localhost.kitchenlab.org> User-Agent: Mutt/1.5.6i Subject: Re: Public Access to Perforce? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Aug 2004 19:06:47 -0000 --mR8QP4gmHujQHb1c Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Aug 18, 2004 at 08:48:04AM -0700, Bruce A. Mah wrote: > As you pointed out later on, converting the entire repository is a > pretty big task, although I've heard several times about developers in > the Subversion community using the FreeBSD CVS repository as test data.= =20 That's mostly because it's extremely polluted. Branch and tag names are mixed all over the place. That doesn't sit well with the normal subversion tree style, due to name collisions. I know this because I tried to convert it to svn some time ago. FreeBSD's repository needs a slightly different svn repository layout than usual in order for it to work. :-/ However, perhaps svn is not the best choice, in fundamental style. As a diverse project, FreeBSD should support remote, loosely coupled repositories based on the main one. I believe svn doesn't work well for that purpose. Regards, --=20 wca --mR8QP4gmHujQHb1c Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFBI6jFF47idPgWcsURAjsCAJ98D61bew+CvBqvnBXtq8mazHC3+gCfelmv Vd6LBNfCzaum2o8QVoCo180= =EsZP -----END PGP SIGNATURE----- --mR8QP4gmHujQHb1c--