Re: Repeated merge strategies

Zack Weinberg wrote:

>I *think* it's plausible to do merge arrows, and in fact ancestor
>sets, entirely with revision properties. For MRA functionality, all
>you need is a 'svn:mergedfrom' prop on the merged revision that points
>to the indirect ancestor. AS is a bit trickier; you put a list of
>(merge start, merge end, add/subtract) tuples as properties on the
>merged revision, and walk up the revision graph building the set.
>
>

I'd be scared to use properties for this, for two reasons. One is
implementation-specific -- the way we store properties makes them
unsuitable for large amounts of data. The other has to do with
semantics: If you want to stay sane while managing a plethora of
extraneous surplussage of branches, you have to be able to do complex
queries in the merge history. Props simply weren't designed for that.

Come to think of it, that's an implementation-specific reason, too...

-- 
Brane Čibej   <brane_at_xbc.nu>   http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org