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

Re: 'svn status -u -v', behavior and APIs

From: Mark Phippard <MarkP_at_softlanding.com>
Date: 2005-10-04 00:13:56 CEST

> It seemed as simple as removing it from svn_wc_status2_t. As it's
> present in svn_wc_entry_t (which svn_wc_status2_t includes as "entry"),
> you'll always have the information available after filling in the
> information for either type.

The problem with this approach is the scenario when the command is showing
you info about a new item in the repository. In that scenario the
svn_wc_entry_t is currently null because there is no entry in the WC. We
did not feel comfortable changing this into a partially populated
structure. This was also the main scenario where Subclipse absolutely
needs to get a URL and Node kind. That is why we needed the second URL and
kind fields. So, the only way the second URL can be removed is if you are
willing to have svn_wc_entry_t in the structure that only has the URL
populated (when it is a new file in the repository).

> Given that we believe that both sets of information -- WC plus repos --
> should be available from the API, and we have some wiggle room still with
> JavaHL, what would you think a modified JavaHL API which can provide both
> WC and repos info in a single call should look like?

I think the basic approach you were taking is fine.


Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Oct 4 00:14:40 2005

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.