Anthony Edward Cooper wrote:
> Hi again,
>
> Just recently had an odd one. A developer on our team got a `file
> .... modified during commit, aborting' message.
Happened to me too in 0.36, and it was fault of wrong inodeprints (and
refresh_inodeprints didn't solve the problem).
Deleting (and recreating) them solved the issue. I don't remember
exactly how they come to corrupt in fact. =(
Lapo
_______________________________________________
Monotone-devel mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/monotone-devel
