[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: Peter N. Lundblad <peter_at_famlundblad.se>
Date: 2005-10-04 08:52:16 CEST

On Mon, 3 Oct 2005, Mark Phippard wrote:

> > It seemed as simple as removing it from svn_wc_status2_t. As it's
> already
> > 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).
>
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.

Regards,//Peter

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