From: Stefan Sperling [mailto:s...@elego.de]
Sent: Wednesday, July 27, 2016 11:55 AM
> Setting the corrupted working copy problem aside, the assertion failure is
> likely a bug in TortoiseSVN in the way it calls Subversion's public API
> function svn_client_cleanup2(). TortoiseSVN should be
> pa
From: Stefan Sperling [mailto:s...@elego.de]
Sent: Wednesday, July 27, 2016 11:45 AM
> Altogether. Store working copies on local disk (or something which
> *really* looks like a local disk) if at all possible.
Thanx, but that won't work for me. Network drive is backed up daily, while I
have no b
On Wed, Jul 27, 2016 at 08:02:07AM +, Thomsen, Allan A B wrote:
> Hi,
>
> I encountered this issue on 1.9.3 and upgraded to 1.9.4 - no difference
>
> If I do a cleanup I get:
> Quote
> Subversion reported the following
> (you can copy the content of this dialog
> to the clipboard using Ctrl-C
On Wed, Jul 27, 2016 at 09:24:08AM +, Thomsen, Allan A B wrote:
> Is the general recommendation against using network drives all together or
> just when there is a risk of multiple instance access?
Altogether. Store working copies on local disk (or something which
*really* looks like a local d
From: Stefan Sperling [mailto:s...@elego.de]
Sent: Wednesday, July 27, 2016 10:51 AM
> We generally recommend against storing working copies on network drives
> because sqlite has problems with this: http://sqlite.org/faq.html#q5
Makes sense for shared locations. My network drive is my home dire
On Wed, Jul 27, 2016 at 08:02:07AM +, Thomsen, Allan A B wrote:
> The place the files are stored is on a network drive.
We generally recommend against storing working copies on network
drives because sqlite has problems with this: http://sqlite.org/faq.html#q5
6 matches
Mail list logo
