Rebased to current master (cb8418) as atomic-new-v4 (aka for-review/atomic-new-v4).
On Wed, May 4, 2011 at 4:30 PM, Austin Clements <amdragon at mit.edu> wrote: > jrollins found a timing bug in the atomicity test. ?A fix, plus beefed > up test comments are on a new atomic-new-v3 (and > for-review/atomic-new-v3) branch at > ?http://awakening.csail.mit.edu/git/notmuch.git/ > Since this is more than a rebase, I'll email an update to the one > changed patch in the series. > > On Tue, Apr 26, 2011 at 12:13 AM, Austin Clements <amdragon at mit.edu> wrote: >> Bump. ?Now rebased against current head (with no conflicts) on >> atomic-new-v2 (and for-review/atomic-new-v2) at >> ?http://awakening.csail.mit.edu/git/notmuch.git/ >> >> On Fri, Feb 18, 2011 at 2:58 AM, Austin Clements <amdragon at mit.edu> wrote: >>> This patch series modifies notmuch new to perform all operations >>> atomically and to perform maildir flag synchronization eagerly. ?As a >>> result, notmuch new can be interrupted without risking database >>> consistency or losing track of messages, but still without losing >>> progress in the middle of a big import. ?This also paves the way for >>> fixing the antisocial locking behavior of notmuch new. >>> >>> While there are quite a few patches in the series, each one is >>> bite-sized and you can see the number of atomicity violations dropping >>> with nearly every patch using the test added by the first patch. >>> >>> On my test machine, these patches have no affect on performance. >>> >>> These patches are also available on the atomic-new-v1 branch at >>> ?http://awakening.csail.mit.edu/git/notmuch.git/ >>> >>> _______________________________________________ >>> notmuch mailing list >>> notmuch at notmuchmail.org >>> http://notmuchmail.org/mailman/listinfo/notmuch >>> >> >