Re: tree conflict use cases

On 10/31/07, Stefan Sperling <stsp@elego.de> wrote:

> (Also, I guess we will need to partially track renames on the
> server side as well for some use cases, but more on that later.
> I don't really want to talk about design ideas before that community
> has accepted the use cases. So far there hasn't been much feedback...)

There hasn't been much feedback so far because

(a) we've discussed these use cases before, for long periods of time

(b) the collective energy & attention of this developer community is
limited; we're all incredibly focused on finishing svn 1.5 right now
-- lots of frantic polishing and debugging going on.

So it's just a matter of timing. Now is not a good time to open up a
blue-sky discussion of how to re-design large pieces of subversion's
architecture. :-) Maybe after 1.5 is released?

Incidentally, one of the things I've worked on in svn 1.5 is a
tree-conflict of sorts: making the server and client deal (more
correctly) with the situation where 'svn update' wants to move a file
which you've locally modified. Rather than 'unversion' your modified
file, and add a new file, libsvn_wc now attempts to move your modified
file to the new name.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Oct 31 14:44:04 2007