Johan Corveleyn <jcorvel_at_gmail.com> writes:
> On Tue, Jul 9, 2013 at 9:20 PM, Alexander Haley <ahaley_at_meditech.com> wrote:
>> test, and compare the xml outputs. For me (on a Win XP 32bit machine), they
>> differ in a very key fashion:
>>
>> "old" xml (just a leading excerpt)
>>
>> <?xml version="1.0" encoding="UTF-8"?>
>> <status>
>> <target
>> path="C:\svnfocus\versions\version8\dev">
>> <entry
>> path="C:\svnfocus\versions\version8\dev">
>> ...
>> ...
>>
>> THE KEY bit is the PATH="" parts . notice how they specific a full absolute
>> path? Then, contrast to the "new" xml output:
>>
>>
>> <?xml version="1.0" encoding="UTF-8"?>
>> <status>
>> <target
>> path="C:\svnfocus\versions\version8\dev">
>> <entry
>> path="..\..\..\svnfocus\versions\version8\dev">
>> ...
>> ...
>>
>>
>> NOW SEE how the target and entry paths differ. The entry path possess
>> enough ..\ "parent" folder references to "dig out of the" Program
>> Files\TortoiseSVN\bin path all the way back up to the point from which the
>> \svnfocus\versions\version8\dev path might be constructed. I've
>> experimented moving the execution directory around - i.e. executing the svn
>> command from C:\ or C:\OTHER\FOLDER\PATH , and the ..\..\ changes
>> accordingly.
>>
>> Any advice or followup requests?
>
> This strikes me as a quite strange and unexpected change of behavior.
> I'm not sure if it was intentional. Since no one responded for a
> couple of days with the answer to the "intentional" question, I'd say:
> please file an issue.
I could not get this to happen on Linux. Are you using the same path in
the checkout and status commands? Can you provide a complete recipe?
Something to do with drive letters, or case differences perhaps?
--
Philip Martin | Subversion Committer
WANdisco | Non-Stop Data
www.wandisco.com
Received on 2013-07-15 23:22:10 CEST