Julian Foad <julianfoad_at_btopenworld.com> writes:
> I think this achieves:
>
> * An improvement in WC API self-consistency, and thereby a
> simplification of calling code in users such as svn_client_cat() and
> svn_client_propget().
>
> * A way to access text conflict artifact files that is consistent with
> how we access text base files.
>
> * A way to access property conflict artifacts which we will want to
> store soon, however we choose to store them, that is consistent with how
> we access base and working properties.
>
> * An identification mechanism that we can also apply to tree conflict
> artifacts. Although difficult-to-resolve tree conflicts may occur less
> often than "normal" conflicts, when it does occur the need to access
> these things through a consistent programmatic interface may be greater
> than the need currently is for text and prop conflicts.
Agreed. But, couple of thoughts:
- No need for "_rev", just call it "svn_wc_kind_t" :-)
- To convert all the existing code to use this sounds like a truly
stunning amount of work. Am I overestimating? Is this getting
close to the amount of work required for libsvn_wc_ng?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-07-21 21:27:33 CEST