Append-only weavefiles

[Aaron Bentley]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

John Arbash Meinel wrote:
> The magic is in the "operations" line. Basically, it just encodes what
> operations are necessary to recreate the weave. It is able to recreate
> the in-memory weave (by reading the entire file).
> 
> The offsets are based on the in-memory weave. I thought it would be nice
> to do them based solely on the previous ancestry. Which might mean that
> you didn't have to read the entire file.
> I also don't know if there are better in-memory representations, but
> since Martin had already done all the work of making this one work, I
> just stuck with it.

So what operations require building the entire reading the entire file?

Weavediff uses relative offsets so that you can work with partial
information. E.g, you can produce an annotated revision from partial
information.  You can also do weave merge with partial information.

I have a preliminary implementation of it here:

http://panoramicfeedback.com/opensource/weavediff/

I was going to wait until weaves had landed before I worked on it, though.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDNiNI0F+nu1YWqI0RAjd1AJ91RX550mHN5nS3IZMPHkTzd1kUhwCfbVWg
m7fsD3OJlmFdYpZlc5RYWXw=
=wRoi
-----END PGP SIGNATURE-----