Franz Sirl wrote on Tue, 24 Jul 2018 22:00 +0200:
> It turns out this is probably issue #4700 which for some reason was
> never approved for the 1.9 branch, even though it was already nominated
> last October. So the version that matters here is the server version.
> After I upgraded the server
Am 2018-07-21 um 16:27 schrieb Franz Sirl:
Am 2018-07-20 um 16:46 schrieb Franz Sirl:
Am 2018-07-20 um 15:55 schrieb Branko Čibej:
On 20.07.2018 15:37, Franz Sirl wrote:
Hi,
this already happened a few times here, but now I managed to re-create
it reliably.
This happens at least on Linux
Am 2018-07-20 um 16:46 schrieb Franz Sirl:
Am 2018-07-20 um 15:55 schrieb Branko Čibej:
On 20.07.2018 15:37, Franz Sirl wrote:
Hi,
this already happened a few times here, but now I managed to re-create
it reliably.
This happens at least on Linux with subversion-1.8/subversion-1.10 and
on
Am 2018-07-20 um 15:55 schrieb Branko Čibej:
On 20.07.2018 15:37, Franz Sirl wrote:
Hi,
this already happened a few times here, but now I managed to re-create
it reliably.
This happens at least on Linux with subversion-1.8/subversion-1.10 and
on Windows
with TortoiseSVN-1.9, didn't test older
On 20.07.2018 15:37, Franz Sirl wrote:
> Hi,
>
> this already happened a few times here, but now I managed to re-create
> it reliably.
> This happens at least on Linux with subversion-1.8/subversion-1.10 and
> on Windows
> with TortoiseSVN-1.9, didn't test older versions yet. Server is
>
Hi,
this already happened a few times here, but now I managed to re-create
it reliably.
This happens at least on Linux with subversion-1.8/subversion-1.10 and
on Windows
with TortoiseSVN-1.9, didn't test older versions yet. Server is
subversion-1.9.5
on Linux, a "svnadmin verify" of a
