6
Make sure that dev3 handles the rich root correctly. That is that upgrades set
7
the new value correctly and that commits to a non-rich-root followed by
8
deserialisation show the root as having changed, diffs between non rich root
9
revisions should not? show the root as changing?
12
* Network stream form. Possibly just the gc group. Possibly a cluster of gc
13
groups with bzip2 over them. Possibly a gc group but with fulltexts that the
14
target has stripped out and replaced with an 'external' record.
16
* Consider a more 'binary' layout for things like sha1 sums, or length
19
* Investigate sha1 overhead. Currently when doing 'bzr pack' we sha once on
20
extraction, and then one more time on insertion. Removing both calls saves
21
6s out of 32s for 'bzr pack' (and 8s=>5.5s for 'repository-details')