[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-04 19:27:54 CEST

On Tue, 04 Oct 2005, Peter N. Lundblad wrote:
> > 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).
> Can't we just rename the URL field from ood_url to url and always populate
> it with the entries URL. We can share this data with the svn_wc_entry if
> it exists, so the cost is just an extra pointer in the svn_wc_status2_t
> struct.

We could do this Peter, though it would slightly complicate the
implementation in that the data for that field might come from the
repository in the case of a new item having been added to the repository
since the last update of the working copy (which is effectively an out of
date WC).

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Oct 4 19:27:26 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.