Following the sentiments expressed in http://groups.google.com/group/visualsvn/browse_thread/thread/1ec5ae554c53f03c, here's an update on this issue, for the benefit of other group members.
I've had a dialogue with Visual SVN support and they've been working on a fix. A specific release of 2.5.2 did not resolve this issue and the production 2.5.2 release still produces the same error usually once every 2 days or so. The issue remains outstanding. On Nov 9, 8:21 am, VisualSVN Team <supp...@visualsvn.com> wrote: > Replied directly by a private e-mail. > > Please use our feedback form for submitting support > requests:http://www.visualsvn.com/support/feedback/ > > -- > With best regards, > Pavel Lyalyakin > VisualSVN Team -- You received this message because you are subscribed to the Google Groups "VisualSVN" group. To post to this group, send email to visualsvn@googlegroups.com. To unsubscribe from this group, send email to visualsvn+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/visualsvn?hl=en.
