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

Re: Prototype design for merge tracking in Subversion

From: Branko ─îibej <brane_at_xbc.nu>
Date: 2006-02-13 03:13:59 CET

David James wrote:
> I'd like to help design a toy SVK-like wrapper around Subversion,
> which stores merge-tracking information in an SQL database. This toy
> program could be developed quickly without worrying about compatibility
> concerns, and serve as a prototype for our final merge-tracking
> implementation.
>
> I've outlined a potential database format for this SVK-like wrapper
> program below. Please review this format and check whether it could help
> us solve merge tracking.
>

I think you're going about this the wrong way.

Second of all, an SVK-like wrapper (with its own database, even) isn't
going to solve merge tracking in *Subversion*, however hard you try.
This is something we have to solve on the repository and/or client
library level, not in some add-on tool.

But first of all, you can't just come up with some database schema to
"solve merge tracking" without first spelling out the actual problems
you're trying to address. Starting on any kind of prototype without
doing the necessary design work first is the worst possible thing we
could do for SVN, because we're almost guaranteed to screw up along the
way, and we'd get yet another can of worms to fix in 2.0.

If you want an example of how to do these things right, take a look at
the locking design discussions.

-- Brane

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Feb 13 03:14:19 2006

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.