> -----Original Message-----
> From: cz02 [mailto:c...@cdak.net]
> Sent: woensdag 22 mei 2013 12:21
> To: users@subversion.apache.org
> Subject: Strange log "path not found" behaviour
>
> I'm getting a strange log path not found behaviour if I query for
> multiple revisions:
>
> i:\>svn log https://server/svn/core/base/trunk -r7114
> ------------------------------------------------------------------------
>
> i:\>svn log https://server/svn/core/base/trunk -r6818
> ------------------------------------------------------------------------
> r6818 | chris | 2012-05-31 15:27:16 +0200 (Thu, 31 May 2012) | 1 line
>
> ##################
> ------------------------------------------------------------------------
>
> i:\>svn log https://server/svn/core/base/trunk -r6818 -r7114
> ------------------------------------------------------------------------
> r6818 | chris| 2012-05-31 15:27:16 +0200 (Thu, 31 May 2012) | 1 line
>
> ##################
> svn: E160013: '/svn/core/!svn/rvr/7114/trunk' path not found
>
> i:\>svn log https://server/svn/core/base/trunk -r7114 -r6818
> svn: E160013: '/svn/core/!svn/rvr/6818/base/trunk' path not found
>
> (I've replaced the actual message with #)
>
> The path changed between the two revisions (trunk was moved to
> base/trunk).
>
> Running the log separately is OK but I get an error when combining them
> - shouldn't they both behave the same way?
>
> SVN 1.7.9 server+client on Windows
> (http://sourceforge.net/projects/win32svn)
Yes it should behave the same way, but there were some issues in the
implementation. When multiple revisions are passed we try to optimize the
way to calculate the actual url to perform the operation on.
This case was recently fixed (and then further optimized for performance)
towards the soon to be released 1.8.
I'm not sure if the relevant fixes are easy to backport to 1.7.x.
(cc: pburba)
Bert
>
> -chris
