Yes, and I don't know how that folder was created.
2014-12-18 23:04 GMT+02:00 Ryan Schmidt :
>
> Please remember to Reply All so that your reply also goes to the mailing
> list, not just to me.
>
> > On Dec 18, 2014, at 2:54 PM, Anton Lee wrote:
> >
> > Hello.
> > I was doing "svn status" on windo
Please remember to Reply All so that your reply also goes to the mailing list,
not just to me.
> On Dec 18, 2014, at 2:54 PM, Anton Lee wrote:
>
> Hello.
> I was doing "svn status" on windows.
> Yes problem is repeatable.
> And I found why it was crashing. Somehow I had folder named
> "C:\Users
What were you doing when this crash occurred? Is the problem repeatable?
svn-crash-log20141218133900.dmp
Description: Binary data
svn-crash-log20141218133900.log
Description: Binary data
On 17.12.2014 15:29, Charlie Smurthwaite wrote:
Hi Charlie,
Thanks for the report and in particular for providing a solution to it.
I hadn't seen this effect on any of my numa workstations so far to
this extend. So, take all the feedback and suggestions in this post
with great caution.
On 17/
Subversion 1.8.10 is used.
I changed several properties of the file in one working copy and commit.
Then I changed also these several properties in another working copy and
update.
This resulted in a file with property conflict status (as expected). But
when I execute "svn info --xml" for this fil