Excerpts from Moritz Wilhelmy's message of 2011-02-13 08:59:12 -0500: > Excerpts from John Wyzer's message of Sun Feb 13 09:20:13 +0100 2011: > > So the question remain - if messags are missing from one Maildir, is my only > > option to dump, reindex all and restore? That would be painful given the > > number of messages... > > Not only painful and annoying but also very stupid. Why would someone want to > get rid of sup-sync --changed? It happens all the time that Maildirs are > externally changed, there *should* be some easy way to sync these changes > back, > at least that's my insignificant opinion. I don't completely understand the > motivation for getting rid of this feature in the first place. Can someone > please explain?
sup-sync --changed was removed because it is no longer necessary. The maildir code can now gracefully deal with messages being moved and deleted. If all locations for a message are deleted it will keep the index entry (including the snippet) but display an error (inline, not disrupting the rest of the UI) if you try to view the message. Is this the behavior you're seeing, or is there a bug in the implementation? Sascha posted a patch that deletes index entries with no locations after a sync. I'd rather see that as a extra sup-sync --purge option, and if you don't want deleted messages to appear in the UI we should just check for that before adding them to the ThreadSet. _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
