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

Inconsistencies in svn_client_info_3

From: Markus Schaber <m.schaber_at_3s-software.com>
Date: Mon, 29 Aug 2011 11:33:38 +0200


(This is a slightly enhanced repost.)

I'm using latest build of SharpSVN against SVN 1.7.

I'm using SvnClient.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 calling svn_client_info_3 on a working

When I pass no peg_revision, and set 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.

However, when I set revision to svn_opt_revision_working or
svn_opt_revision_base (which both should be local operations as well),
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 "some/path/foo", then the first
entry "some/path/foo" will have "foo" as path, and all others will be
relative to "foo", like "some/path/foo/bar" will be displayed as "bar".)

Additionally, wc_info is not set, despite "base" and "working" being
local revisions.

Is this the intended behavior?

Best regards

Markus Schaber

We software Automation.

3S-Smart Software Solutions GmbH
Markus Schaber | Developer
Memminger Str. 151 | 87439 Kempten | Germany | Tel. +49-831-54031-0 |
Fax +49-831-54031-50

Email: m.schaber@3s-software.com | 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-29 11:34:38 CEST

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.