Lightweight branches?

Aaron Bentley aaron.bentley at utoronto.ca
Thu Nov 16 00:22:53 GMT 2006


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

Martin Pool wrote:
> On 15 Nov 2006, Aaron Bentley <aaron.bentley at utoronto.ca> wrote:
> The "collation" storage format we discussed in Sydney goes towards this
> in a couple of ways, and I've started some code for it.

Is there anywhere I can read about it?

> There are two assumptions our storage layer makes that (it seems to me)
> need to be relaxed to do history horizons.  They are that there's a
> single knit file per file_id, and that the storage layer's indexing is
> overloaded to also describe the ancestry graph.  Instead we should be
> able to group together historic data more flexibly so we can have old
> history in a separate location or not present at all.

I'd always imagined doing this sort of thing at a higher level, e.g.
repository vs storage layer.

> Another example of this is that knits are required to store accurate
> annotations.

I would really like to keep that requirement in future formats, because
it means that a common base is not necessary to perform a merge.  I
don't think it's much of a burden.  Am I missing something?

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

iD8DBQFFW69c0F+nu1YWqI0RAnP2AJ9U3RnVSkxO4DAePfFhSDOlHvhnFACfQsSv
zc/Fn24b5lyvaoWGhmCOZg0=
=+BVE
-----END PGP SIGNATURE-----




More information about the bazaar mailing list