On 11.06.2015 12:56, Daniel Shahaf wrote:
> Branko Čibej wrote on Thu, Jun 11, 2015 at 09:01:01 +0200:
>> On 10.06.2015 19:34, Stefan Kueng wrote:
>>>
>>> On 10.06.2015 19:06, Bert Huijben wrote:
Hi Dean,
There is not much we can do about this. The Subversion apis re
Branko Čibej wrote on Thu, Jun 11, 2015 at 09:01:01 +0200:
> On 10.06.2015 19:34, Stefan Kueng wrote:
> >
> >
> > On 10.06.2015 19:06, Bert Huijben wrote:
> >> Hi Dean,
> >>
> >> There is not much we can do about this. The Subversion apis require that
> >> you pass canonical urls,
On 10.06.2015 19:34, Stefan Kueng wrote:
>
>
> On 10.06.2015 19:06, Bert Huijben wrote:
>> Hi Dean,
>>
>> There is not much we can do about this. The Subversion apis require that
>> you pass canonical urls, while the client (TortoiseSVN) that you use
>> doesn’t canonicalize the url
What do you expect the api to canonicalize things like “h” or "” to?
We can’t make everything a valid url… That is simply impossible. You need to
pass something that at least looks like a url. The canonicalize api just
forcesany urls that point to the same location to use the same canonical
fo
On 10.06.2015 21:04, Bert Huijben wrote:
I don’t think we can really fix that url in the api by canonicalizing it
to something completely different/unrelated, but the assertion makes it
obvious that the caller can just see/check that the url is not going to
work… just like values such as the em
I don’t think we can really fix that url in the api by canonicalizing it to
something completely different/unrelated, but the assertion makes it obvious
that the caller can just see/check that the url is not going to work… just like
values such as the empty string or strings with no scheme, that
On 10.06.2015 19:06, Bert Huijben wrote:
Hi Dean,
There is not much we can do about this. The Subversion apis require that
you pass canonical urls, while the client (TortoiseSVN) that you use
doesn’t canonicalize the url before passing it to this api.
And that's what the svn
appear when attempting to open
repository with bad URL
Upgraded & tested with same bad URL ... same result - although assertion error
now occurs on a different line.
Badly formatted URL: "file:///c:Software/SourceCodeRepository
"
---
Subver
Upgraded & tested with same bad URL ... same result - although assertion error
now occurs on a different line.
Badly formatted URL:
"file:///c:Software/SourceCodeRepository"
---
Subversion Exception!
---
Subversion encountered a serious problem.
P
9 matches
Mail list logo
