On Thu, 2010-06-17, rhuij...@apache.org wrote: > Author: rhuijben > Date: Thu Jun 17 10:40:30 2010 > New Revision: 955542 > > URL: http://svn.apache.org/viewvc?rev=955542&view=rev > Log: > Introduce a new svn_client_status_t structure to separate the public > client status api from the implementation of status in libsvn_wc, to > allow further cleanup in libsvn_wc. Note that this libsvn_client > function still uses relative paths in its api to avoid breaking > third party code even more than necessary for removing entries.
[...] Hi Bert. Very good work! > URL: > http://svn.apache.org/viewvc/subversion/trunk/subversion/include/svn_client.h?rev=955542&r1=955541&r2=955542&view=diff > ============================================================================== > --- subversion/trunk/subversion/include/svn_client.h (original) > +++ subversion/trunk/subversion/include/svn_client.h Thu Jun 17 10:40:30 2010 > @@ -1843,6 +1843,183 @@ svn_client_commit(svn_client_commit_info > */ > > /** > + * Structure for holding the "status" of a working copy item. > + * > + * The item's entry data is in @a entry, augmented and possibly shadowed > + * by the other fields. @a entry is @c NULL if this item is not under > + * version control. That paragraph appears to be obsolete. > + * @note Fields may be added to the end of this structure in future > + * versions. Therefore, to preserve binary compatibility, users > + * should not directly allocate structures of this type. > + * > + * @since New in 1.7. > + */ > +typedef struct svn_client_status_t > +{ [...] - Julian