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
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
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: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
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
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 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: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
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 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 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 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
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 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
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
Stefan Sperling wrote:
>On Fri, Nov 02, 2018 at 02:30:17PM +, Lorenz wrote:
>> Hi all,
>>
>> I've defined attributes on parts in the schematic editor.
>>
>> Now I'm trying to show them in the layout running an ULP on the
>> grouped parts in the board editor or from the contex menu.
>>
>> Wi
16 matches
Mail list logo
