Branko Čibej wandisco.com> writes:
>
> On 07.09.2015 10:45, Daniele Pedroni wrote:
> > Hi Ivan,
> >
> > yes, definitely, thank you a lot!
> >
> > So, if I got your point, with your updated svn.exe I'll be able to
test if command line work properly, but
> I'll have to wait for TortoiseSVN update
On 07.09.2015 10:45, Daniele Pedroni wrote:
> Hi Ivan,
>
> yes, definitely, thank you a lot!
>
> So, if I got your point, with your updated svn.exe I'll be able to test if
> command line work properly, but I'll have to wait for TortoiseSVN update to
> use it? Or the latter relies on the same svn.
Hi Ivan,
yes, definitely, thank you a lot!
So, if I got your point, with your updated svn.exe I'll be able to test if
command line work properly, but I'll have to wait for TortoiseSVN update to use
it? Or the latter relies on the same svn.exe so it should work as well after
the update?
Daniel
Hi Ivan,
thank you very much, but honestly speaking I don't know how to test it: I
installed SVN server through Redmine Bitnami package, and I update SVN on my PC
using TortoiseSVN installer.
If you provide me some suggestions about how to test it, I'll try it!
Looking forward to hear from you
Yes Bert, you’re right, my explanation wasn’t 100% clear: I meant that everyone
who pointed out this issue was using SVN on network drives.
I’m using svnserve service on a windows 2003 server with F-Secure 11.01; my PC
has Windows 7 x64 with F-Secure 12.00. I tried disabling the antivirus on my
