-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sat, 11 Nov 2006 01:58:19 +0000, Russ wrote:
> Its really a matter of taste... If the client code shares nothing I common
> with each other the you probably would want multiple repositories.
>
> Keeping things in one repo let's you merge certain changes between
> clients... It simplifies management of the repository, especially if you
> have the same access rules for each repo.
>
> There are some cons to keeping thing in one repository. The bigger it
> gets, arguably the slower it gets. I have nothing to support this, just a
> gut feeling. You can't delete things from the repository other then using
> the clunky svndumpfilter. If you have a client who leaves, his project
> will forever be in the repository taking up space.
>
> Other then that, I can't think of any good reasons to have separate
> repositories.
>
One more point. It is fairly easy to merge several repositories together
later if you want them together for some reason, but splitting up a
repository after copies and moves around the repository have been made
becomes essentially impossible.
- --
Kenneth P. Turvey <kt-usenet@squeakydolphin.com>
XMPP: kpturvey@jabber.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
iD8DBQFFVrCSi2ZgbrTULjoRAntxAJ0TSvrYxfLUnmEql4OQrrgxIX8+0wCfdESx
m3RWFWORD/rn3w9iyyaCU1U=
=6lmy
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Nov 12 06:28:26 2006