On 09.05.2012 11:12, Stefan Sperling wrote:
Stefan, could you please file an issue for this? Someone will take
a look at this eventually. Thanks.
Done: http://subversion.tigris.org/issues/show_bug.cgi?id=4182
Stefan Sperling wrote on Wed, May 09, 2012 at 11:12:10 +0200:
> On Wed, May 09, 2012 at 11:09:35AM +0300, Daniel Shahaf wrote:
> > Hi, just wanted to say thanks for the effective bug report.
>
> Yes, it is very good indeed.
>
> > I'm not able to look further into this right now but I hope someone
On Wed, May 09, 2012 at 11:09:35AM +0300, Daniel Shahaf wrote:
> Hi, just wanted to say thanks for the effective bug report.
Yes, it is very good indeed.
> I'm not able to look further into this right now but I hope someone else will.
Stefan, could you please file an issue for this? Someone will
Hi, just wanted to say thanks for the effective bug report. I'm not
able to look further into this right now but I hope someone else will.
Daniel
Stefan Podskubka wrote on Wed, May 09, 2012 at 09:20:59 +0200:
> Hello,
>
>> So maybe it is related to the server version and the communication
>> p
Hello,
So maybe it is related to the server version and the communication
protocol.
I have made Wireshark captures for the failed and for the successful
communication.
If anyone is interested in those captures please say so, I didn't want
to send them directly to the list.
Anyway, if the bug
Hello list,
I tried coming up with a simple repro-script but there it worked, of
course...
I didn't manage to reproduce the error with the file:// protocol, but
with http:// I was able to reproduce it.
Still on Windows 7, still using subversion 1.7.4 on the client and
subversion 1.4.3 on the
