thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=0.9_rc1 2011-09-24T23:26:42Z 2011-09-24T23:26:42Z David Bremner bremner@debian.org 2011-09-24T19:13:49Z urn:sha1:0ce713ae02a2f2fc326d9c04bf9bf95123f228c0 This bump is because of the new symbols introduced by the atomicity patches. 2011-09-24T23:00:29Z Austin Clements amdragon@mit.edu 2011-06-11T19:34:11Z urn:sha1:35f4a0f18b2484e835e8b647f3d2c2782efcc406 State up front that these functions may add a filename to an existing message or remove only a filename (and not the message), respectively. Previously, this key information was buried in return value documentation or in "notes", which made it seem secondary to these functions' semantics. 2011-09-24T23:00:28Z Austin Clements amdragon@mit.edu 2011-06-11T04:42:58Z urn:sha1:51c3c0b2d27c8d0ba8e1ae242fd907c59f82d992 Adding a message may involve changes to multiple database documents, and thus needs to be done in a transaction. This makes add_message (and, I think, the whole library) atomicity-safe: library callers only needs to use atomic sections if they needs atomicity across multiple library calls. 2011-09-24T23:00:28Z Austin Clements amdragon@mit.edu 2011-06-11T04:19:31Z urn:sha1:7a8046ced8c0e61ddd0ff463cfc17ed63e6edad3 notmuch_database_find_message_by_filename is mostly stolen from notmuch_database_remove_message, so this patch also vastly simplfies the latter using the former. This API is also useful in its own right and will be used in a later patch for eager maildir flag synchronization. 2011-09-24T01:50:39Z Austin Clements amdragon@mit.edu 2011-06-11T04:07:54Z urn:sha1:bfe4555325086d5cb99e3962424128f94d1c921d Previously, notmuch_database_remove_message would remove the message file name, sync the change to the message document, re-find the message document, and then delete it if there were no more file names. An interruption after sync'ing would result in a file-name-less, permanently un-removable zombie message that would produce errors and odd results in searches. We could wrap this in an atomic section, but it's much simpler to eliminate the round-about approach and just delete the message document instead of sync'ing it if we removed the last filename. 2011-09-24T01:50:39Z Austin Clements amdragon@mit.edu 2011-02-06T09:17:49Z urn:sha1:e4379c43e21ff69dcdb66064fe3de83ae0642fc0 Make _notmuch_message_remove_filename return NOTMUCH_STATUS_DUPLICATE_MESSAGE_ID if the message has more filenames and fix callers to handle this. 2011-09-24T01:50:38Z Austin Clements amdragon@mit.edu 2011-06-11T03:35:06Z urn:sha1:e59cc0031fbf84f49e32dedb9927f427d2c49309 notmuch_database_t now keeps a nesting count and we only start a transaction or commit for the outermost atomic section. Introduces a new error, NOTMUCH_STATUS_UNBALANCED_ATOMIC. 2011-09-24T01:50:38Z Austin Clements amdragon@mit.edu 2011-01-29T16:25:24Z urn:sha1:957f1ba3fc1d737887029ff1787fc6bea94de00b These operations translate into non-flushed Xapian transactions, allowing arbitrary groups of database operations to be performed atomically. 2011-09-13T02:36:00Z Austin Clements amdragon@mit.edu 2011-06-10T19:58:18Z urn:sha1:62445dd0231c4f9e49f0be293e9f539d63bfdc99 Previously, this function would synchronize the folder list even if removing the file name failed. Now it returns immediately if removing the file name fails. 2011-09-05T10:44:14Z David Bremner bremner@debian.org 2011-09-05T03:19:32Z urn:sha1:9db21452721356be5169254cd7e8c0ec5b25066b If the configure script detects missing getline and/or getdelim symbols, then notmuch will use it's own versions. This patch, based on id:"87k49v12i5.fsf@pc44es141.cs.uni-magdeburg.de" by Matthias Guedemann, adds the symbols to notmuch.sym as well so they are properly exported from the library.