Re: [Monotone-devel] resolving name conflicts; schema_migration test broken

[Zack Weinberg]

On Sat, May 17, 2008 at 6:19 PM, Stephen Leake
<address@hidden> wrote:
> The problem in schema_migration is that both the revision format _and_
> the database schema change during the test. Because of the change in
> revision_format number, all the revids change between the two
> databases that are supposed to be the same.
>
> I think we need a way to request revision_format 1 for this test.

I haven't been following this discussion very closely, so I don't know
what you changed in the revision format, but that's beside the point.
Can you make it so that monotone generates revision_format 2 *only if*
the revision itself has content unrepresentable in format 1?  That
should make this problem vanish, and also maximizes interoperability -
we have netsync compatibility between old and new as long as you don't
try to transfer a revision with the new thing.

zw