Re: dump & load

> > I'm thinking about something slightly different: maintaining two
> > repositories side-by-side, one of them being the working repository,
> > and the other being for read-only access. From time to time I'd take,
> > for example, 10.000 revisions from the bottom of the working copy,
> > and move them to the top of the read-only version.
>
> Oh, you want *replication* from one server to another.
>
> You should come into IRC sometime. People have reinvented solutions to

Erm.. I'm there most of the time. :-)

> this over and over... we have 'svnpush' in our source tree (which could
> be run as a post-commit hook.) svk does this too. And someone recently
> wrote a bourne script to do this as well, runnable from a cron job.

This is very interesting, but not really what I have in mind in this
case. I'm interested in cutting the bottom of the working repository to
maintain it below some given size (10GB, 20GB, 50GB, I don't know). As I
said, this is just an idea right now. I'll have to think further about
the advantages and consequences.

-- 
Gustavo Niemeyer
http://niemeyer.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org