On 19.12.2018 09:18, Thorsten Schöning wrote:
> Guten Tag Thorsten Schöning,
> am Mittwoch, 21. November 2018 um 15:23 schrieben Sie:
>
>> News:
> The following arrived today:
>
>> Just wanted to let you know that this issue should now be resolved!
>> Let us know how you go.
>> Cheers,
>> Simon
>>
Guten Tag Thorsten Schöning,
am Mittwoch, 21. November 2018 um 15:23 schrieben Sie:
> News:
The following arrived today:
> Just wanted to let you know that this issue should now be resolved!
> Let us know how you go.
> Cheers,
> Simon
> GitHub Support
Things seem to work again for me using th
On 10.12.2018 15:09, Nathan Hartman wrote:
> On Mon, Dec 10, 2018 at 5:14 AM Stefan Sperling wrote:
>
>> Perhaps Github's customers will just need to press a little bit
>> harder for a fix to be applied at Github's end?
>
> Agreed. The squeaky wheel gets the grease.
GitHub has fixed their Subvers
On Mon, Dec 10, 2018 at 5:14 AM Stefan Sperling wrote:
> Perhaps Github's customers will just need to press a little bit
> harder for a fix to be applied at Github's end?
Agreed. The squeaky wheel gets the grease.
On 10.12.2018 10:08, Thorsten Schöning wrote:
> 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 inc
On Mon, Dec 10, 2018 at 10:08:10AM +0100, Thorsten Schöning wrote:
> 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 bridg
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
On Mon, Dec 10, 2018 at 12:30 AM Branko Čibej wrote:
>
> On 09.12.2018 23:41, Nico Kadel-Garcia wrote:
> > On Sun, Dec 9, 2018 at 1:27 PM Branko Čibej wrote:
> >> On 09.12.2018 19:14, Thorsten Schöning wrote:
> >>> Guten Tag Thorsten Schöning,
> >>> am Mittwoch, 21. November 2018 um 15:23 schrieb
On 09.12.2018 23:41, Nico Kadel-Garcia wrote:
> On Sun, Dec 9, 2018 at 1:27 PM Branko Čibej wrote:
>> On 09.12.2018 19:14, Thorsten Schöning wrote:
>>> Guten Tag Thorsten Schöning,
>>> am Mittwoch, 21. November 2018 um 15:23 schrieben Sie:
>>>
> Thanks for following up. Our engineers have been
On Sun, Dec 9, 2018 at 1:27 PM Branko Čibej wrote:
>
> On 09.12.2018 19:14, Thorsten Schöning wrote:
> > Guten Tag Thorsten Schöning,
> > am Mittwoch, 21. November 2018 um 15:23 schrieben Sie:
> >
> >>> Thanks for following up. Our engineers have been able to reproduce
> >>> the error on our CI sy
On 09.12.2018 19:14, Thorsten Schöning wrote:
> Guten Tag Thorsten Schöning,
> am Mittwoch, 21. November 2018 um 15:23 schrieben Sie:
>
>>> Thanks for following up. Our engineers have been able to reproduce
>>> the error on our CI system and are working on a fix.
> Another two weeks have passed wit
Guten Tag Thorsten Schöning,
am Mittwoch, 21. November 2018 um 15:23 schrieben Sie:
>> Thanks for following up. Our engineers have been able to reproduce
>> the error on our CI system and are working on a fix.
Another two weeks have passed without any hint to the status of this
problem from GH an
On 22.11.2018 17:39, Nico Kadel-Garcia wrote:
> On Wed, Nov 21, 2018 at 9:54 AM Branko Čibej 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
On Wed, Nov 21, 2018 at 9:54 AM Branko Čibej 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
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 s
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
On 15.11.2018 19:07, 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?
> Sadly not and they didn't get in contact with you using dev@?
Nope; not now, and not ever. Sigh.
--
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?
Sadly not and they didn't get in contact with you using dev@? I've
looked at that once in a while but couldn't see anything of interest.
Mit freundlichen
On 05.11.2018 18:27, Thorsten Schöning wrote:
> Guten Tag Ryan Schmidt,
> am Montag, 5. November 2018 um 04:45 schrieben Sie:
>
>> I'd be interested to know the resolution, since I use the GitHub
>> svn bridge daily. I'll hold off on upgrading past Subversion 1.10.x
>> for now but could you keep us
On 04.11.2018 20:11, Branko Čibej wrote:
> On 04.11.2018 18:57, Thorsten Schöning wrote:
>> Guten Tag Branko Čibej,
>> am Sonntag, 4. November 2018 um 17:47 schrieben Sie:
>>
>>> I'm not sure what you mean by "handles more than only DAV successfully"
>> I thought it might be possible that GitHub an
On Mon, Nov 5, 2018 at 12:27 PM Thorsten Schöning wrote:
>
> Guten Tag Ryan Schmidt,
> am Montag, 5. November 2018 um 04:45 schrieben Sie:
>
> > I'd be interested to know the resolution, since I use the GitHub
> > svn bridge daily. I'll hold off on upgrading past Subversion 1.10.x
> > for now but
Guten Tag Ryan Schmidt,
am Montag, 5. November 2018 um 04:45 schrieben Sie:
> I'd be interested to know the resolution, since I use the GitHub
> svn bridge daily. I'll hold off on upgrading past Subversion 1.10.x
> for now but could you keep us informed about what GitHub does to solve this?
Suppo
Guten Tag Ryan Schmidt,
am Montag, 5. November 2018 um 04:45 schrieben Sie:
> I'd be interested to know the resolution, since I use the GitHub
> svn bridge daily. I'll hold off on upgrading past Subversion 1.10.x
> for now but could you keep us informed about what GitHub does to solve this?
Pleas
On 05.11.2018 04:45, Ryan Schmidt wrote:
>
> On Nov 4, 2018, at 11:57, Thorsten Schöning wrote:
>
>> Now "we" need to get GitHub to change their
>> implementation and I didn't even get an automatic bot-reply to my
>> question on Friday yet. :-) Lets see how things are going after I send
>> them thi
On Nov 4, 2018, at 11:57, Thorsten Schöning wrote:
> Now "we" need to get GitHub to change their
> implementation and I didn't even get an automatic bot-reply to my
> question on Friday yet. :-) Lets see how things are going after I send
> them this thread...
I'd be interested to know the reso
Thorsten Schöning wrote on Sun, 04 Nov 2018 18:57 +0100:
> Guten Tag Branko Čibej,
> am Sonntag, 4. November 2018 um 17:47 schrieben Sie:
>
> > I'm not sure what you mean by "handles more than only DAV successfully"
>
> I thought it might be possible that GitHub answers differently but
> properly
On 04.11.2018 18:57, Thorsten Schöning wrote:
> Guten Tag Branko Čibej,
> am Sonntag, 4. November 2018 um 17:47 schrieben Sie:
>
>> I'm not sure what you mean by "handles more than only DAV successfully"
> I thought it might be possible that GitHub answers differently but
> properly, because the ot
Guten Tag Nico Kadel-Garcia,
am Sonntag, 4. November 2018 um 19:42 schrieben Sie:
> Can you switch to using TortoiseGit locally, and avoid the extra
> compatibility layers?
My use case might be special: I have one large libs-repo for many
different projects and that contains committed libs and so
On Sun, Nov 4, 2018 at 10:05 AM Thorsten Schöning wrote:
>
> Hi all,
>
> GitHub documents to support Subversion clients and I'm using that for
> many projects to include them in one of my working copies using
> svn:externals. Since upgrading TortoiseSVN from 1.10 to 1.11 I get the
> following erro
Guten Tag Branko Čibej,
am Sonntag, 4. November 2018 um 17:47 schrieben Sie:
> I'm not sure what you mean by "handles more than only DAV successfully"
I thought it might be possible that GitHub answers differently but
properly, because the other check mentioned something about HTTP v2.
Because of
On 04.11.2018 17:41, Branko Čibej wrote:
> On 04.11.2018 16:05, Thorsten Schöning wrote:
>> Hi all,
>>
>> GitHub documents to support Subversion clients and I'm using that for
>> many projects to include them in one of my working copies using
>> svn:externals. Since upgrading TortoiseSVN from 1.10
On 04.11.2018 17:47, Branko Čibej wrote:
> On 04.11.2018 17:06, Thorsten Schöning wrote:
>> Guten Tag Thorsten Schöning,
>> am Sonntag, 4. November 2018 um 16:42 schrieben Sie:
>>
>>> Others have the same problem and while it is true that GitHub might
>>> have implemented something on their own, it
On 04.11.2018 17:06, Thorsten Schöning wrote:
> Guten Tag Thorsten Schöning,
> am Sonntag, 4. November 2018 um 16:42 schrieben Sie:
>
>> Others have the same problem and while it is true that GitHub might
>> have implemented something on their own, it might help to have a look
>> at the changes bet
On 04.11.2018 16:05, Thorsten Schöning wrote:
> Hi all,
>
> GitHub documents to support Subversion clients and I'm using that for
> many projects to include them in one of my working copies using
> svn:externals. Since upgrading TortoiseSVN from 1.10 to 1.11 I get the
> following error for all of t
Guten Tag Thorsten Schöning,
am Sonntag, 4. November 2018 um 16:42 schrieben Sie:
> Others have the same problem and while it is true that GitHub might
> have implemented something on their own, it might help to have a look
> at the changes between 1.10 and 1.11 regarding the protocol.
Guess I fo
Thorsten Schöning wrote on Sun, Nov 04, 2018 at 16:42:11 +0100:
> Guten Tag Thorsten Schöning,
> am Sonntag, 4. November 2018 um 16:05 schrieben Sie:
>
> >> The server at '[...]' does not support the HTTP/DAV protocol.
>
> Others have the same problem and while it is true that GitHub might
> have
Guten Tag Thorsten Schöning,
am Sonntag, 4. November 2018 um 16:05 schrieben Sie:
>> The server at '[...]' does not support the HTTP/DAV protocol.
Others have the same problem and while it is true that GitHub might
have implemented something on their own, it might help to have a look
at the chang
Hi all,
GitHub documents to support Subversion clients and I'm using that for
many projects to include them in one of my working copies using
svn:externals. Since upgrading TortoiseSVN from 1.10 to 1.11 I get the
following error for all of those projects:
> The server at '[...]' does not support
38 matches
Mail list logo
