They recommend setting up a "pre-revprop-change" script with nothing in it but
the initial "shebang", for each target repository, and then using "svnsync" to
migrate the repositories. It also assumes the existence of an "svnsync" user-ID
on the target system, which (at least assuming it's an o
On Jul 27, 2017, at 14:23, James H. H. Lampert wrote:
>
> They recommend setting up a "pre-revprop-change" script with nothing in it
> but the initial "shebang", for each target repository, and then using
> "svnsync" to migrate the repositories.
Sounds plausible. An empty pre-revprop-change ho
UNCLASSIFIED
Hi,
svn-win32-1.88
I am not subscribed to the mailing list and would appreciate being cc:ed in any
response.
I have a service that uses svn_client_status5 to determine the current state of
a subversion working copy. Even though I have several thousand files in the
working copy, t
Greetings.
My employer has put me on a project of moving our SVN and Trac servers
from the old Windows Server 2003 box on which they're currently running
over to a Google Compute Engine instance.
To that end, I've set up the instance using Bitnami's canned Trac image,
which includes SVN 1.9.
Hi,
"CCD Systems Help Desk" wrote:
> Subject: Please publish unsubscribe information in the patch update mailings.
>
> We no longer require updates for SubVersion, please remove us from the
> mailing list.
Please read: http://subversion.apache.org/mailing-lists.html
Andreas
