notmuch/bindings, branch 0.36thread-based email index, search, and tagginghttps://git.notmuchmail.org/git/notmuch/atom?h=0.362022-04-25T11:45:12Zversion: bump to 0.362022-04-25T11:45:12ZDavid Bremnerdavid@tethera.net2022-04-25T11:45:12Zurn:sha1:f93a2c7383439305dc2cbbd18243fb8cb3c0feb2version: bump to new release candidate2022-04-16T11:26:27ZDavid Bremnerdavid@tethera.net2022-04-16T11:26:27Zurn:sha1:8f9dbff49e8097f223296504465fa449c3111023version: bump to 0.36~rc02022-04-15T11:42:22ZDavid Bremnerdavid@tethera.net2022-04-15T11:42:22Zurn:sha1:d87d780ef00af603366a71ec958a7f4a31545171python-cffi: use config_pairs API in ConfigIterator2022-02-17T01:57:22ZDavid Bremnerdavid@tethera.net2022-02-09T12:28:54Zurn:sha1:9ddd13f75827f4972872c8766320c7cb80b1819b
This returns all of the config keys with non-empty values, not just
those that happen to be stored in the database.
version: bump to 0.352022-02-06T17:11:32ZDavid Bremnerdavid@tethera.net2022-02-06T17:11:32Zurn:sha1:b87373f8c41fb8014b7e756fba1e942410209bfbversion: bump to 0.35~rc02022-01-29T22:12:58ZDavid Bremnerdavid@tethera.net2022-01-29T22:12:58Zurn:sha1:addeb11e37b0fff06211b1756d021732730ce0ee
Start release process for 0.35
lib/open: no default mail root in split configurations2022-01-15T19:59:39ZDavid Bremnerdavid@tethera.net2021-12-25T13:33:05Zurn:sha1:fad2e7540bf9309bfb335650ded753e9ed085eff
If we know the configuration is split, but there is no mail root
defined, this indicates a (lack of) configuration error. Currently
this can only arise in XDG configurations.
Merge tag '0.34.3'2022-01-09T23:34:58ZDavid Bremnerdavid@tethera.net2022-01-09T23:34:58Zurn:sha1:63d3b2b5cf8702b5fecea77392ce46f8a8249175
notmuch 0.34.3 release
version: bump to 0.34.32022-01-09T19:35:12ZDavid Bremnerdavid@tethera.net2022-01-09T19:35:12Zurn:sha1:a226b7a29b8977003081d96850a1f9e2b9a962b9bindings/python-cffi: search for config by default2022-01-09T19:16:51ZDavid Bremnerdavid@tethera.net2022-01-08T21:21:43Zurn:sha1:8b737af28bc377db3e661a5744f3b7479b7ce485
The previous (pre-0.34.2) constructor searched for a config file but
only if the database path was not specified, and only to retrieve
database.path. Neither of the available options (CONFIG.SEARCH or
CONFIG.NONE) matches this semantics exactly, but CONFIG.SEARCH causes
less breakage for people who relied on the old behaviour to set their
database.path [1]. Since it also seems like the friendlier option in
the long run, this commit switches to CONFIG.SEARCH as default.
This requires a certain amount of updating the pytest tests, but most
users will actually have a config file, unlike the test environment.
[1]: id:87fsqijx7u.fsf@metapensiero.it