On Mon, 23 May 2022 11:03:32 +, "Morin, Michael"
wrote:
>>On Mon, May 23, 2022 at 6:16 AM Morin, Michael
>>wrote:
>>>
>>> In my case, I have no choice in the matter of what server and OS to move
>>> to. We dont use VisualSVN.
>>>We just use Tortoise with Subversion. When we last >did a m
Hi,
> We just use Tortoise with Subversion.
You mean just plain file:// access? (no mod_dav_svn or svn)? Then there is not
even a Subversion server involved. Is there any way you can re-use the hostname?
Andreas
Yes, each repository is a distinct Subversion repository. We have about 300
Subversion users located in different departments and 171 repositories.
-Original Message-
From: Nico Kadel-Garcia
Sent: Monday, May 23, 2022 6:58 AM
To: Morin, Michael
Cc: users@subversion.apache.org
Subject:
On Mon, May 23, 2022 at 6:16 AM Morin, Michael wrote:
>
> In my case, I have no choice in the matter of what server and OS to move to.
> We don’t use VisualSVN. We just use Tortoise with Subversion. When we last
> did a migration from one Windows server to another, it was a tedious process
> of
In my case, I have no choice in the matter of what server and OS to move to. We
don't use VisualSVN. We just use Tortoise with Subversion. When we last did a
migration from one Windows server to another, it was a tedious process of
contacting the users of the repository, asking them if the repo
Hi,
> If you have not used any of the advanced features in VisualSVN [...]
FWIF... The free VistualSVN version can* be set up to do full write-through
proxying and async replication. It ships all the modules. (* last confirmed in
~2015)
Andreas
