[Monotone-devel] propagate oddities (bugs?), sure lca bugs

[Christof Petig]

While trying to demonstrate monotone propagate to a friend I stumbled
over some problems:

Monotone-viz shows propagate nodes as rectangles but merge nodes as
circles. This indicates that there is a difference in data structures
but I can't imagine the semantical difference (I used (the 3 argument)
explicit_merge as an emergency fallback which did exactly what I
(thought I) asked propagate to do).

But since I did not write down the proposed heads* to merge I can only
guess/hope that at least _they_ were correctly chosen (since the merge
already happened in my database I cannot reproduce the command). Though
Monotone chose (and will choose) the wrong ancestor, that I can tell for
sure:

monotone lca e3623ca77d2a8b45817ecaa5b67018c453652830
7d5918d0181f7bb9adba2ee63234146d23bcf83e

should be 0b17415d7aa112060e8ead9ae7a486510dc61a9d
but is ce860bae312c4bb8483d5b3b2a8cd3bebe2323d5

So to make a long email short:
- I can give a reproducible failure for the lca algorithm (in HEAD)
- The difference between propagate and explicit merge is strange to me

    Christof

PS: My CVS client class [net.venge.monotone.cvssync] can already
successfully retrieve all necessary information (changelog, -time,
author, tags, file contents/patches) for a full import from a remote
1.11 or 1.12 cvs server.

* both net.venge.monotone and n.v.m.cvssync had only one head at the
time (see IDs above)

signature.asc
Description: OpenPGP digital signature