Re: svn_client_log3() doesn't work as advertised

Philip Martin <philip@codematters.co.uk> writes:

> $ svn log -vq wc/bar@3 -r2:1
> ../svn/subversion/libsvn_client/ra.c:821: (apr_err=195012)
> svn: Unable to find repository location for 'file:///home/pm/sw/subversion/obj/repo/bar' in revision 2
>
> That looks like a bug to me.

I now think it was designed to work like this. Issue 1970 was quite
explicit that given this:

   r1 add /foo
   r2 delete /foo
   r3 something
   r4 add /bar (copied from /foo@1)

then both "svn cat -r4 bar@4" and "svn cat -r1 bar@4" show a file but
"svn cat -r3 bar@4" is an error.

However I do think that log and peg revisions are odd. Consider

   r1 add /foo
   r2 modify /foo
   r3 delete /foo
   r4 add /foo (different from r1)
   r5 add /bar (copied from /foo@2)

svn log foo shows r4 and that seems OK

svn log foo@2 shows r2, r1 and that seems a bit odd if
                           foo is a wc path, although it probably
                           makes sense if foo is an URL.

svn log foo@2 -rHEAD:1 shows r4 and that seems wrong

svn log bar shows r5, r2, r1 and that seems OK

svn log bar -r3:1 gives an error and that seems wrong

I've never really looked at the history tracing code before and I
can't really determine whether this behaviour is correct. Can anyone
else explain it?

-- 
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org