Re: [Monotone-devel] Re: Support for binary files, scalability and Windows port

[Zack Weinberg]

Ori Berger <address@hidden> writes:

> If you have a persistent suffix tree (one tree for the _entire_
> repository), when you want to put a new version in the database, you
> just start walking the tree, and note what part of it you take from
> what repository file. Renames, copies, splits, merges, etc. will all
> be efficiently represented (in terms of "delta" storage) even
> without any explicit "monotone rename" command.
>
> Your elevator pitch includes "ancestry is just some interesting
> metadata", and this is just taking it to the extreme ... A version is
> stored as a patchwork of parts of all previous files, with or without
> any ancestry knowledge.

Ooh! Does this mean you can notice when someone's moved a chunk of
text from file A to file B, and describe the change as such in a
sufficiently powerful "cvs annotate"-on-steroids interface?

zw