<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/lib, branch 0.23.7</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.23.7</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.23.7'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2017-02-22T10:28:03Z</updated>
<entry>
<title>lib: fix g_hash_table related read-after-free bug</title>
<updated>2017-02-22T10:28:03Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2017-02-22T10:17:47Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=4e649d000b9d3764aea98cb0e1120947d7f76f3d'/>
<id>urn:sha1:4e649d000b9d3764aea98cb0e1120947d7f76f3d</id>
<content type='text'>
The two g_hash_table functions (insert, add) have different behaviour
with respect to existing keys. g_hash_table_insert frees the new key,
while g_hash_table_add (which is really g_hash_table_replace in
disguise) frees the existing key. With this change 'ref' is live until
the end of the function (assuming single-threaded access to
'hash'). We can't guarantee it will continue to be live in the
future (i.e. there may be a future key duplication) so we copy it with
the allocation context passed to parse_references (in practice this is
the notmuch_message_t object whose parents we are finding).

Thanks to Tomi for the simpler approach to the problem based on
reading the fine glib manual.
</content>
</entry>
<entry>
<title>lib: document API added in 0.23</title>
<updated>2016-10-07T01:46:01Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2016-10-05T01:12:56Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=b2d6f07a028a443c2f96e1684be5ec3addb55d96'/>
<id>urn:sha1:b2d6f07a028a443c2f96e1684be5ec3addb55d96</id>
<content type='text'>
The API was already documented, but for future readers note when the
functions were added,
</content>
</entry>
<entry>
<title>require xapian &gt;= 1.2.6</title>
<updated>2016-10-07T01:45:46Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2016-10-05T00:35:23Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=af8903df34647d9456e8f3fe26a164959969b451'/>
<id>urn:sha1:af8903df34647d9456e8f3fe26a164959969b451</id>
<content type='text'>
It seems that no-one tried to compile without Xapian compact support
since March of 2015, since that's when I introduced a syntax error in
that branch of the ifdef.

Given the choice of maintaining this underused branch of code, or
bumping the Xapian dependency to a version from 2011, it seems
reasonable to do the latter.
</content>
</entry>
<entry>
<title>lib: bump minor version to mark added symbols</title>
<updated>2016-10-02T01:19:07Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2016-10-02T01:11:56Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=c2e74662bbbbf9be1fde0ae416dc2664ba3da3cd'/>
<id>urn:sha1:c2e74662bbbbf9be1fde0ae416dc2664ba3da3cd</id>
<content type='text'>
This should not change the SONAME, and therefore won't change the
dynamic linking behaviour, but it may help some users debug missing
symbols in case their libnotmuch is too old.
</content>
</entry>
<entry>
<title>lib/database.cc: fix misleading indentation</title>
<updated>2016-09-28T11:14:08Z</updated>
<author>
<name>Tomi Ollila</name>
<email>tomi.ollila@iki.fi</email>
</author>
<published>2016-09-27T15:06:52Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=1c3a8e0898be614b5183f0ae626386f7746e7e07'/>
<id>urn:sha1:1c3a8e0898be614b5183f0ae626386f7746e7e07</id>
<content type='text'>
Found by gcc 6.1.1 -Wmisleading-indentation option (set by -Wall).
</content>
</entry>
<entry>
<title>lib: add talloc reference from string map iterator to map</title>
<updated>2016-09-24T13:08:45Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2016-09-23T09:33:19Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=514a0a6a3bd74c03db6cd9b28edc0a29a8a2441e'/>
<id>urn:sha1:514a0a6a3bd74c03db6cd9b28edc0a29a8a2441e</id>
<content type='text'>
This is needed so that when the map is modified during traversal, and
thus unlinked by the database code, the map is not disposed of until the
iterator is done with it.
</content>
</entry>
<entry>
<title>add property: query prefix to search for specific properties</title>
<updated>2016-09-21T21:14:25Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2016-07-08T09:15:36Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=693ca8d8a80438ce1e361e7e6d22288f52a11c55'/>
<id>urn:sha1:693ca8d8a80438ce1e361e7e6d22288f52a11c55</id>
<content type='text'>
We want to be able to query the properties directly, like:

   notmuch count property:foo=bar

which should return a count of messages where the property with key
"foo" has value equal to "bar".
</content>
</entry>
<entry>
<title>lib: iterator API for message properties</title>
<updated>2016-09-21T21:14:25Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2016-06-13T01:05:52Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=58fe8fce1d1b7b86b4914a5a476ff21411c84082'/>
<id>urn:sha1:58fe8fce1d1b7b86b4914a5a476ff21411c84082</id>
<content type='text'>
This is a thin wrapper around the string map iterator API just introduced.
</content>
</entry>
<entry>
<title>lib: extend private string map API with iterators</title>
<updated>2016-09-21T21:14:24Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2016-06-13T01:05:51Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=b846bdb48233c907d1ecaff495fbf6bc578910d6'/>
<id>urn:sha1:b846bdb48233c907d1ecaff495fbf6bc578910d6</id>
<content type='text'>
Support for prefix based iterators is perhaps overengineering, but I
wanted to mimic the existing database_config API.
</content>
</entry>
<entry>
<title>lib: basic message-property API</title>
<updated>2016-09-21T21:14:24Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2016-06-13T01:05:50Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=b8bb6d796458732622f80464dd808b3e02f57d9d'/>
<id>urn:sha1:b8bb6d796458732622f80464dd808b3e02f57d9d</id>
<content type='text'>
Initially, support get, set and removal of single key/value pair, as
well as removing all properties.
</content>
</entry>
</feed>
