Serf and Tree Conflicts for 1.6

        Hi,

Looking at some of the issues reported by the serf buildbot it looks
like the tree conflict support requires some kind of ordering in the
received changes that serf does not provide.
(I'm not sure if this are the delta editor requirements of earlier
threads)

Without changes in either the tree conflicts handling (the way tree
conflicts on parents are cached in the batton) or serf (the ordering of
child items) we can't fix these issues for 1.6.

If this issue is really that ordering issue talked about earlier (Can
somebody confirm this) we should discuss how to go forward with:
A) Relaxing the requirements of the delta editor and fixing the tree
conflict handling to match the new requirements.
B) Fixing serf to the old requirements.

Or in my opinion the worst solution:
C) Fixing the tree conflicts handling, but keeping serf incompatible
with the current delta editor requirements.

In my opinion we should choose one route or the other, but we can't just
ignore this problem. Especially if we want to make serf the default DAV
layer.

        Bert

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-11-27 11:30:28 CET