Thomas Keller <[EMAIL PROTECTED]> writes: > The problem is already "fixed" on mainline and goes into 0.37. The > roster which is attached to each revision is not removed, thus if you > try to commit the same revision again it cannot store the roster (which > has then the same revid) again. The fix now just checks if the roster > exists before a revision is committed, and if it exists, skips this step. > > There have been long discussions and explanations why we do not remove > the roster on kill_rev_locally, please search the mail archive if > interested in the conclusions.
Thanks. I approve of not removing the roster and the fix is just fine. BTW, I was not really complaining as the workaround I described (syncing into a fresh database) was rather straightforward. -- Ludovic Brenta. _______________________________________________ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
