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

Re: [Subclipse-dev] Enhancement needed in svn status -u

From: Peter N. Lundblad <peter_at_famlundblad.se>
Date: 2005-08-11 08:20:09 CEST

On Wed, 10 Aug 2005, Mark Phippard wrote:

> My initial thought/hope was that the client API had the info that was
> needed and JavaHL just needed to be revved to pass it back. I thought
> that svn st -u -v was showing the revision of the item in the repository.
> Sussman pointed out to me on IRC that this is not the case. We are
> currently working on a design proposal for revving the client API to
> include information about the repository item in the information it
> returns. We are just trying to wrap our heads around it right now.
>
I don't think you need to rev the client API. You can add fields to the
end of svn_wc_status2_t (that's even documented!).

This chage seems pretty straight forward to me. Just add the fields you
need, and catch the entryprops in change_file_prop and change_dir_prop in
libsvn_wc/status.c. The URL field is a little tricky because of switched
entries. For entries that exist in the WC, it is readily available. For
added paths, there must be a nearest ancestor in the WC with an URL that
you can extend.

Hope this gives some hints,
//Peter - who recently messed with status -u for locking...
Received on Thu Aug 11 16:20:09 2005

This is an archived mail posted to the Subclipse Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.