compressed weaves, and revision.weave

[Aaron Bentley]

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

John A Meinel wrote:
> Only if you actually did real ancestry. The current weave format only
> shares lines between parents and their children.

Okay, I get it now.  Neat hack.

> I could certainly make it "BASE-not-really-a-revision-please-ignore-me".

I think something like that would be safer.  Though even Arch's
!!!nothing-should-depend-on-this field did manage to leak out.

> The reason I didn't want to do real ancestry is because you certainly
> could never say that all of the ancestry will be present. I might sign
> my entries, but you wouldn't sign yours, etc.

I think that's only a problem if you store something for all the
revisions.  It would work if you stored only the last-signed revision,
just as we only store the last-modified revision for file contents.

> Do you want me to changed the name?

Yeah, if we go ahead with your idea, it would be safest to avoid any
valid revision ids, I think.

> Right now I'm having the text for the "null:" signature be the sha1 hash
> of nothing.

Another interpretation of the null revision would be:
<revision committer="" format="5"
inventory_sha1="e89199a707b4b58b8d48b0681fc20462612738e3"
revision_id="null:" timestamp="0">
<message></message>
</revision>

(that sha1 is wrong, though.)

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

iD8DBQFDXUO+0F+nu1YWqI0RAphvAJ4zJFdiJFagu8Y/+s7N3G9e7ahMgACcD1lP
C/HSjmfZb4/r3tT29tPCqh0=
=BKzv
-----END PGP SIGNATURE-----