On 11/20/07, Mark Phippard <markphip@gmail.com> wrote:
> On Nov 20, 2007 9:43 AM, Stefan Sperling <stsp@elego.de> wrote:
> > On Tue, Nov 20, 2007 at 01:21:55AM +0000, Julian Foad wrote:
> > > Sorry, I'm being facetious, but you get the idea: unless I'm
> > > missing something, there ought to be a programmatic WC API for listing the
> > > conflicts.
> >
> > The problem is that CollabNet needs something that is compatible
> > with 1.5, so we cannot extend the API. I know this sounds crazy,
> > and I'd rather be able to design away without having to worry
> > about API changes, but our task at hand is about getting it to
> > work somehow so it can be integrated into 1.5.x.
>
> Huh? We do not do custom versions of Subversion. Anything you are
> doing should be based on trunk and normal release cycle expectations.
> In this case, that would ideally be for the 1.6 release, but 1.7 if it
> comes to that. You should be able to add any API's that are in
> agreement with the normal Subversion API compatibility promises.
Since we already have a wc-version bump on our hands, I'd like to
suggest we change the on-disk entries structure where required to make
our life as simple as possible. This is -in libsvn_wc- already hard
enough.
bye,
Erik.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Nov 20 16:28:04 2007