Date: Wed, 18 Aug 2004 14:06:46 -0500 From: Will Andrews <will@csociety.org> To: current@FreeBSD.org Subject: Re: Public Access to Perforce? Message-ID: <20040818190646.GF90227@sirius.firepipe.net> In-Reply-To: <1092844084.705.7.camel@localhost.kitchenlab.org> References: <Pine.NEB.3.96L.1040818112543.55952C-100000@fledge.watson.org> <1092844084.705.7.camel@localhost.kitchenlab.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040818190646.GF90227>