Comment 2 for bug 152360

Was this introduced by your changes?

I know KnitRepository1 does not have a knit associated with the tree root, while we have one for KnitRepository3.
It may be that when Robert removed the physical KnitRepository3 class, he didn't realize this difference between the two.

Actually, having a knit for the root revision is *why* KR3 is a watershed upgrade. Because once you have one and you do a commit, you start recording different data than you can represent in KR1.

I will agree that this is a critical issue. As it sounds like you cannot branch from a KR1 repo.