Michael <tigris@zzZZzz.net> writes:
> I've been reading a discussion about a "proper" backup tool and now I'm
> wondering if I misunderstand something in the nature of svn... Can
> someone explain what is wrong with this backup policy... Say, I want to
> keep a copy of repository. To make it harder -- remote one. Isn't it
> achieved with something like
>
> RREV="`ssh user@host "svnlook youngest /repo"`"
> REV="`svnlook youngest /repo`"
> if [ "${REV}" != "${RREV}" ] ; then
> REV="`expr ${REV} + 1`"
> ssh user@host "svnadmin dump /repo -r ${REV}:HEAD --incremental" \
> | svnadmin load /repo
> fi
>
> Well, of course, one can add conditional creation of the local repo,
> more error checking would make sense, maybe, setting umasks if needed,
> and even compression filter, but those are unnecessary details.
>
> Wouldn't this pattern get you a proper copy of the repository?
(Note that I've rethreaded this to users@.)
This should work fine. Of course, watch out that the user has the
exact right permissions for that repository, otherwise it's easy for
things to get messed up.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jul 2 20:49:26 2004