On Wed, Apr 22, 2009 at 09:26:22AM +0200, Adeodato Simó wrote: > Right. My question is what happens if I do, say: > > laptop% smd-push > laptop% smd-pull # this brings message M as new > laptop% read mail, including message M > server% read mail, inclluding message M; flag message M > laptop% smd-push > laptop% smd-pull
So, your question is, what happens if there is a conflict (in VCS terminology). So far there is no "smart" conflict solver, the software just tells you what is wrong, and which files (mails) are interested. It suggest you to "move away" one of them to finish the sync, then you help yourself (that usually means having on one of the two sides a copy of the same message with different flags, the you run mutt and press d on one of them). I'm not that convinced that the usecase you mention is that common, and at least for me, it seems more a place for software overdesign than software features. Remember here that this is a Mailbox, with an owner... your usecase is something like having 2 checkouts of the same software repository and deliberately making incompatible changes on the 2 checkouts and then committing... would you do that? not that often I bet. I'd like to keep the software simple, so unsless I really face this problem, I would avoid implementing this feature. Moreover, the software is layered: mechanisms are in C (and they are able to give upper layers enough information to detect your pattern), while policies are in a scripting language I like (deliberate choice was Lua) and it should be reasonably easy to not duplicate the message but simply add the flag. In any case, thank you all very much for your comments! -- Enrico Tassi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
