[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: merge tracking use cases

From: Mark Phippard <markphip_at_gmail.com>
Date: 2007-12-01 21:22:22 CET

On Dec 1, 2007 3:42 PM, Daniel Rall <dlr@collab.net> wrote:

> Until then, I'd really appreciate it if folks would hold off on the gloom
> and doom. As always, contributions of code, code review, and design
> suggestions are most appreciated. (Review of issue #2992 seems like some
> lower-hanging fruit; looked like it needs more work to me.)

Thanks for keeping a level head Dan.

Except for the fact that I could not sleep last night, I think this
has all been good. It has reaffirmed that we want to get this right
in 1.5, as well as hopefully stimulating some more eyes to look at the
problems.

I do not think things are nearly as bad as they seem. Just in the
last few weeks there have been several major changes made.

First cmpilato went through the code and made it all handle ancestry
properly and not just treat paths as strings. He then made the
changes to copy/move so that they do not need to create mergeinfo.
Meanwhile glasser made all those major changes to SQLite (albeit on a
branch). I think the fact that these sorts of changes can take place
(rather quickly) says something about the code. The interfaces
between layers must be rather solid and we have decent tests in place
to show the functionality that is needed. These are good things.

We clearly still have some problems to solve before we can release.
Let's just work towards solving them. Just because there are some big
problems to still deal with does not mean we have several months of
work left. Let's face it, a lot of this feature has been "grunt
work". Getting tests in place, dealing with edge case, handling
"mundane" things like new notifications, working out what the UI has
to be etc. That work is done, and we have shown we can make major
changes in the algorithms without having to go back and rework all of
that code.

Anyway, I am glad to see people like David Glasser taking a fresh look
about things like SQLite and seeing if there are better/easier ways to
deal with them. Whether we change that or not, the code will be
better for having other options considered. Frankly, it is a lot
easier to do that sort of work now with all of this code in place than
it was 12-18 months ago when this was just starting and some of these
decisions were originally made.

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Dec 1 21:22:32 2007

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.