Re: Problems accessing GitHub's SVN-bridge with SVN 1.11

Guten Tag Branko Čibej,
am Sonntag, 9. Dezember 2018 um 19:27 schrieben Sie:

> My current thinking is that if GitHub can't fix their protocol emulation
> by the time of the planned Subversion 1.12 release, we'll have to
> seriously consider including this patch.

If they really didn't fix it until 1.12, they surely won't ever
anymore. Maybe this gives you enough time to discuss this
fundamentally and tell people what they can expect for issues like
this one in future from the SVN-team?

It seems clear to me that the issue would need to be fixed by GH, but
your are able to workaround it somewhat easily. But this is only one
issue, what in case of another one easy like this or more difficult?
In theory 1.12 could break something different for some reason and
people would need to stick with 1.10 for at least a year then.

If you come to the conclusion that you don't do this kind of hacking
anymore or even at all including this issue, users of the SVN-bridge
would simply need to change their workflow to something else. I'm
only using the bridge because it was the easiest way to stay with my
former workflow and how I manage some versioned libs.

Or do you think it's not worth discussing that fundamentally (yet)?

Mit freundlichen Grüßen,

Thorsten Schöning

-- 
Thorsten Schöning       E-Mail: Thorsten.Schoening_at_AM-SoFT.de
AM-SoFT IT-Systeme      http://www.AM-SoFT.de/
Telefon...........05151-  9468- 55
Fax...............05151-  9468- 88
Mobil..............0178-8 9468- 04
AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow