On Wed, Nov 21, 2018 at 9:54 AM Branko Čibej <brane_at_apache.org> wrote:
>
> On 21.11.2018 15:23, Thorsten Schöning wrote:
> > Guten Tag Branko Čibej,
> > am Donnerstag, 15. November 2018 um 18:21 schrieben Sie:
> >
> >> Has there been any further update from them on this issue?
> > News:
> >
> >> Thanks for following up. Our engineers have been able to reproduce
> >> the error on our CI system and are working on a fix.
> >> This issue is already a focus for our SVN team. However people who
> >> are experiencing this issue can feel free to write in to
> >> support_at_github.com to report their own experience and we'll also let
> >> them know when the issue is fixed.
>
>
> Oh, that's nice.
>
> -- Brane
Can this be entirely sidestepped by using svn+ssh:// access instead of
https:// ? I'm not currently using any Subversion based access to
github, but it might provide a short-term workaround if it's
supported.
Received on 2018-11-22 17:40:08 CET