notmuch, branch 0.21_rc1thread-based email index, search, and tagginghttps://git.notmuchmail.org/git/notmuch/atom?h=0.21_rc12015-10-15T13:09:24Zdebian: update symbols file2015-10-15T13:09:24ZDavid Bremnerdavid@tethera.net2015-10-15T13:09:24Zurn:sha1:127caf7a9ef1c8090f3f1a4e4d5f8c55519a6560
we are only adding symbols, which is exactly the interesting case for a
symbols file.
version: bump to 0.21~rc12015-10-15T11:24:26ZDavid Bremnerdavid@tethera.net2015-10-15T11:16:26Zurn:sha1:627efac85ea3783e9edbb3814d9225c41389df74debian: update changelogs for pre-release2015-10-15T11:14:19ZDavid Bremnerdavid@tethera.net2015-10-15T11:14:19Zurn:sha1:364ab6a225bd539d703164d11b8971d6d5df80b2
a sensible changelog can wait for upstream NEWS to be updated
cli: delete directory documents on directory removal2015-10-14T10:55:41ZJani Nikulajani@nikula.org2015-09-25T20:48:46Zurn:sha1:e26d99dc7b02f33299c281f97a13deaef802bc7a
There was a problem with the directory documents being left behind when
the filesystem directory was removed. This was worked around in [1].
However, that ignored the fact that the directory documents are also
still listed by notmuch_directory_get_child_directories() leading to
confusing results when running notmuch new. The directory documents are
found and queued for removal over and over again.
Fix the problem for real by removing the directory documents. This fixes
the tests flagged as broken in [2].
The (non-deterministic) hack test from [3] also still passes with this
change.
[1] commit acd66cdec075312944e527febd46382e54d99367
[2] commit ed9ceda623d3f22fb66365b33db63c5c982067d3
[3] id:1441445731-4362-1-git-send-email-jani@nikula.org
lib: add interface to delete directory documents2015-10-10T12:14:25ZJani Nikulajani@nikula.org2015-09-25T20:48:45Zurn:sha1:727fcd18c6a3897622582e71a2d71081e3ae40ea
As mentioned in acd66cdec075312944e527febd46382e54d99367 we don't have
an interface to delete directory documents, and they're left behind. Add
the interface.
test: flag one more notmuch new test as broken2015-10-10T12:13:02ZJani Nikulajani@nikula.org2015-09-25T20:48:44Zurn:sha1:0e03ff389443aa062d30e6949bb3220563c474be
Drop the test update added in [1] and mark the test as broken, like the
tests flagged as broken in [2]. These all reflect the same underlying
breakage with (lack of) directory deletion.
[1] commit e4e04bbc328f990e36b77f508aef904d156029b1
[2] commit ed9ceda623d3f22fb66365b33db63c5c982067d3
lib: update doxygen comments to add @since for the new _st API2015-10-05T23:16:59ZDavid Bremnerdavid@tethera.net2015-10-05T23:16:59Zurn:sha1:7a20f26f919a5c30fc53a7cf6f8dd4fbc08dd409
We should probably to this for all new functions introduced from now on.
ruby: use new query_search API2015-10-05T22:54:12ZDavid Bremnerdavid@tethera.net2015-09-27T15:32:03Zurn:sha1:e8a828b30d099b929d2feab0154e98d06786e92e
These changes should not be too surprising for users because the
routines were already potentially throwing exceptions.
lib: migrate thread.cc to new query_search API2015-10-05T22:53:53ZDavid Bremnerdavid@tethera.net2015-09-27T15:32:02Zurn:sha1:378ba492a634db5b841f2454991239a897f830b2
here we rely on thread_id_query being attached to the local talloc
context, so no new cleanup code is needed.
lib: migrate notmuch_database_upgrade to new query_search API2015-10-05T22:53:11ZDavid Bremnerdavid@tethera.net2015-09-27T15:32:01Zurn:sha1:2501c2565ccca19e3e49fa1594aaa90f04e37d6d
Here we depend on the error path cleaning up query