I'm using latest build of SharpSVN against SVN 1.7.
I'm using Client.Info which maps to svn_client_info_3.
It seems that the svn_client_info_receiver2_T parameter abspath_or_url
shows inconsistent behavior when applied to a working copy.
When I pass no peg_revision, and revision to
svn_opt_revision_unspecified, then abspath_or_url will be set to the
absolute path of the file or directory in question, and
svn_client_info2_t->wc_info is set.
When I set revision to svn_opt_revision_working or svn_opt_revision_base
(which both should be local operations), abspath_or_url will contain a
relative path. Even worse, that relative path is relative to parent of
the given path for the directory itself, and relative to the given path
for all other entries. (e. G. if you list directory "foo", than the
first entry will have "foo" as path, and all others will be relative to
"foo".) Additionally, wc_info is not set, despite "base" and "working"
being local revisions.
Is this a known issue?
We software Automation.
3S-Smart Software Solutions GmbH
Markus Schaber | Developer
Memminger Str. 151 | 87439 Kempten | Germany | Tel. +49-831-54031-0 |
Email: firstname.lastname@example.org | Web: http://www.3s-software.com
CoDeSys internet forum: http://forum.3s-software.com
Download CoDeSys sample projects:
Managing Directors: Dipl.Inf. Dieter Hess, Dipl.Inf. Manfred Werner |
Trade register: Kempten HRB 6186 | Tax ID No.: DE 167014915
Received on 2011-08-23 12:48:14 CEST