Hi, Eric Kow <[email protected]> writes: [snip] > I attach the two gzipped inventories. The temp2 one corresponds to the > obliterate and pull approach, and the temp3 to the plain old get > approach. Note that the temp3 one appears to a superset of the temp2 > one. Somehow the temp2 approach breaks up the inventories more that > than the second approach. What exactly is going on? And why does > optimizing the darcs.net repository make this error go away?
I haven't looked in detail, but this sounds like a simple problem: inventories don't get broken on out of order tags, but they do get broken on in-order tags. An in-order tag is one that is below all patches that do not depend on it. (If you think about it, the reasons should be simple enough.) When you do optimize --reorder, all tags are pushed as far down as possible, and inventories are re-broken at these points. Yours, Petr. _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
