On 02.03.2019 15:18, wuzhouhui wrote:
>> On Mar 2, 2019, at 10:09 PM, wuzhouhui wrote:
>>
>>> On Mar 2, 2019, at 9:41 PM, Branko Čibej wrote:
>>>
>>> On 02.03.2019 05:29, wuzhouhui wrote:
> On Mar 2, 2019, at 8:21 AM, Daniel Shahaf wrote:
>
> wuzhouhui wrote on Fri, Mar 01, 2019 at
> On Mar 2, 2019, at 10:09 PM, wuzhouhui wrote:
>
>>
>> On Mar 2, 2019, at 9:41 PM, Branko Čibej wrote:
>>
>> On 02.03.2019 05:29, wuzhouhui wrote:
On Mar 2, 2019, at 8:21 AM, Daniel Shahaf wrote:
wuzhouhui wrote on Fri, Mar 01, 2019 at 17:46:55 +0800:
>> -Original
> On Mar 2, 2019, at 9:41 PM, Branko Čibej wrote:
>
> On 02.03.2019 05:29, wuzhouhui wrote:
>>> On Mar 2, 2019, at 8:21 AM, Daniel Shahaf wrote:
>>>
>>> wuzhouhui wrote on Fri, Mar 01, 2019 at 17:46:55 +0800:
> -Original Messages-
> From: "Branko Čibej"
> Sent Time:
On 02.03.2019 05:29, wuzhouhui wrote:
>> On Mar 2, 2019, at 8:21 AM, Daniel Shahaf wrote:
>>
>> wuzhouhui wrote on Fri, Mar 01, 2019 at 17:46:55 +0800:
-Original Messages-
From: "Branko Čibej"
Sent Time: 2019-03-01 17:16:40 (Friday)
To: users@subversion.apache.org
1-USERTrust RSA Certification Authority.cer
Description: application/x509-ca-cert
2-SSL.com High Assurance CA.cer
Description: application/x509-ca-cert
3-*.apache.org.cer
Description: application/x509-ca-cert
Denis Excoffier wrote on Sat, 02 Mar 2019 09:17 +00:00:
> What would be the best strategy? I can figure out this one:
>
> 1) Within the working copy, delete the existing tree (not svn delete)
> 2) Extract the new tree at the same place
> 3) Interpret the result of 'svn status' in terms of 'svn
wuzhouhui wrote on Sat, 02 Mar 2019 04:29 +00:00:
> In case of someone have interests, you can find my customized Subversion
> in https://github.com/wuzhouhui/subversion.
I think you want svn_io_check_resolved_path() there, no svn_io_check_path().
> Please forgive me about using Git to version
> On 2019-03-01 11:53, Stefan Sperling wrote:
>
>>
>
> Hi Denis,
>
> This problem is not specific to symbolic links.
> There are quite a few cases where --xml produces invalid XML
> when it runs into some kind of error. Perhaps the command
> line client should be fixed to close open XML
