[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: Daniel Rall <dlr_at_finemaltcoding.com>
Date: 2005-10-05 01:10:20 CEST

On Mon, 03 Oct 2005, Daniel Rall wrote:
> > > 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.
> Okay. It felt a little awkward to have no separation in the Status class
> between the WC and repos-supplied information; some of the properties are
> so close in naming that I was wondering if the same WC vs. repos separation
> which is provided by the svn_wc_entry_t and ood_* fields on the
> svn_wc_status2_t shouldn't exist in the Status API as well. For instance,
> add a ReposStatus or Entry inner class; _something_ to help differentiate
> similarly-named fields between the repository and working copy.

Other than the "url" modification, I did not attempt to address this in the
patch I just posted.
Message-ID: <20051004223940.GA3727@despot.finemaltcoding.com>

If I don't get suggestions on how to change this soon, I'm likely to go with
the more monolithic API.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Oct 5 01:09:39 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.