svn_client_log2 doesn't take a peg revision

Hi,

While playing around with the new svn_client_log2() API and its 'limit'
param I noticed that this API doesn't take a peg revision. I think it
should.

If I have a folder which was renamed in revision 100 and the repo is now
at revision 150 I try to do:
svn log path/to/folder --limit=100
<here comes the output>

Now, let's say the output shows me not all the information I hoped for
(maybe because the log message I was looking for wasn't in there. And
no, I assume that the exact log message isn't known so it's not possible
to just get all log messages and search for it)). The last shown log
message is from revision 50.
So I then decide I still need the rest of the log messages:
svn log path/to/folder -r50:0
PROPFIND error (path not found).

With a peg revision, this wouldn't error out but know that the folder
was renamed in revision 100 and still show the logs.

I assume if this get's implemented, it won't make it into 1.2?

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org