[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

svn_client_log3() doesn't work as advertised

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: 2006-04-19 19:36:48 CEST

Hi,

I've reported this issue already 10 days ago
(http://svn.haxx.se/dev/archive-2006-04/0242.shtml), but got no response.
So here goes again:

The new svn_client_log3() API doesn't work as advertised (or as I think
it should work). This new API takes a peg revision, but all my tries
show that the peg revision isn't used at all or makes the log even fail.

For example:
* passing svn_opt_revision_working as the peg revision fails every time.
Seems the local path to a working copy file/folder is first converted to
an URL, and for URLs such a peg revision doesn't make sense. So it fails.

* but even passing svn_opt_revision_number doesn't work over renames.
Take this example:
svnadmin create repo
svn co file:///d:/repo wc
cd wc
svn mkdir trunk
echo test > trunk\file
svn add trunk\file
svn ci -m "log 1"
echo test2 > trunk\file
svn ci -m "log 2"
svn ren trunk\file trunk\file2
svn ci -m "log 3"
echo test > trunk\file2
svn ci -m "log 4"

now an
svn_client_log3("d:/wc/trunk/file2", 4, 2, 1, 100, true, false,
callback, (void*)this, &ctx, pool);
will fail with
"unable to find repository location for file:///d:/repo/trunk/file2 in
revision 2".

So the peg revision is not used at all here.

Can someone please have a look at this? Better now than after releasing
1.4.0.

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
Received on Wed Apr 19 19:39:00 2006

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.