Jim Blandy <email@example.com> writes:
> As I said to Greg H., using ID's as an approximation to node
> similarity is kind of gross. It seems to me that the genetic merge
> tracking info could give us a better approximation to node similarity,
> and also allow us to detect situations like yours. In fact, maybe we
> would toss ID's as keys altogether, and instead use the delta sets as
> keys directly. That would solve this problem, as well as the
> gratuitous asymmetry Greg mentioned.
Karl and I have been reading/studying docs on "changesets".
Yesterday we had a (hand-waving) discussion about how the repository
might implement them as first-class objects. It's interesting, but we
both have a common intuition now that our "genetic merging" idea is
probably 98% equivalent to storing changesets -- they may end up being
the same thing when it comes down to implementation. Pretty neat.
Received on Sat Oct 21 14:36:16 2006