Date: Wed, 18 Aug 2004 21:05:59 -0700 From: "Bruce A. Mah" <bmah@freebsd.org> To: Will Andrews <will@csociety.org> Cc: current@freebsd.org Subject: Re: Public Access to Perforce? Message-ID: <1092888359.62194.7.camel@tomcat.kitchenlab.org> In-Reply-To: <20040818190646.GF90227@sirius.firepipe.net> References: <Pine.NEB.3.96L.1040818112543.55952C-100000@fledge.watson.org> <1092844084.705.7.camel@localhost.kitchenlab.org> <20040818190646.GF90227@sirius.firepipe.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-pWNWEtXI0xCnCl5Fi1/S Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Wed, 2004-08-18 at 12:06, Will Andrews wrote: > 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 Geez, did I really write that this morning?!? Feels like it was at least a couple days ago. > 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. In the normal subversion repository layout (and what's used by cvs2svn by default), branches and tags live in two separate hierarchies, so I'm not sure what kind of collisions you're talking about. I could, however, picture repo-copies and vendor imports showing up in fairly bizarre ways in the converted repository, maybe that's what you were referring to? > 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. :-/ >=20 > 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. That's an interesting question. The usual reaction in the svn community when presented with this point (needing distributed repositories) is "use svk" but I know next to nothing about this tool. (If I had time, I'd JFGI, but...) Cheers, Bruce. --=-pWNWEtXI0xCnCl5Fi1/S Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (FreeBSD) iD8DBQBBJCcn2MoxcVugUsMRAkXcAKC3MDmSbZUVIG6yWF/O7mpbFGPvcACgkQBu po0BXAv7AAZVWy0JA7HaM3A= =s1f/ -----END PGP SIGNATURE----- --=-pWNWEtXI0xCnCl5Fi1/S--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1092888359.62194.7.camel>