On Sun, Aug 2, 2015 at 7:10 PM, Tim Tornid wrote:
> Hello,
>
>
> I had a catastrophic Subversion server loss, and I'm having some troubles
> recovering. The server was using VisualSVN 3.2.3 which is Apache Subversion
> 1.8.13.
>
>
>
What version is the new server running? I'd suggest using the e
On Aug 2, 2015, at 9:10 PM, Tim Tornid wrote:
> I had a catastrophic Subversion server loss, and I'm having some troubles
> recovering. The server was using VisualSVN 3.2.3 which is Apache Subversion
> 1.8.13.
>
> I have a full exact duplicate of the repositories directory, but it's giving
> m
Hi Johan. As I know now there was networking problems with datacenter that
hosts svn repository I worked with. Also I see similar report in this
mailing list so I came to conclusion that this is a key condition for the
bug. But I will report to the TortoiseSVN mailing list as well.
Thanks.
пн, 3
On Wed, Jul 29, 2015 at 3:54 PM, Илья Денисов wrote:
> Hello, everyone. I've got an exception.
> Steps I made:
> * Open trunk history
> * Search for specific commit by typing bug tracker id in filtration bar at
> the top
> * Fetch more commits with "Next 100" button until I saw the commit
> * Open
