<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/lib, branch debian/0.12-1</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=debian%2F0.12-1</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=debian%2F0.12-1'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2012-03-18T10:58:35Z</updated>
<entry>
<title>Fix error reporting in notmuch_database_find_message_by_filename</title>
<updated>2012-03-18T10:58:35Z</updated>
<author>
<name>Justus Winter</name>
<email>4winter@informatik.uni-hamburg.de</email>
</author>
<published>2012-03-17T16:41:27Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=ea54c4fdc7d0ed9a4d6ab328d44c10ce5668d587'/>
<id>urn:sha1:ea54c4fdc7d0ed9a4d6ab328d44c10ce5668d587</id>
<content type='text'>
Formerly it was possible for *message_ret to be left
uninitialized. The documentation however clearly states that "[o]n any
failure or when the message is not found, this function initializes
'*message' to NULL".

Signed-off-by: Justus Winter &lt;4winter@informatik.uni-hamburg.de&gt;
</content>
</entry>
<entry>
<title>Actually close the xapian database in notmuch_database_close</title>
<updated>2012-03-03T15:30:07Z</updated>
<author>
<name>Justus Winter</name>
<email>4winter@informatik.uni-hamburg.de</email>
</author>
<published>2012-03-02T14:58:39Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=cfc5f1059aa16753cba610c41601cacc97260e08'/>
<id>urn:sha1:cfc5f1059aa16753cba610c41601cacc97260e08</id>
<content type='text'>
Formerly the xapian database object was deleted and closed in its
destructor once the object was garbage collected. Explicitly call
close() so that the database and the associated lock is released
immediately.

The comment is a courtesy of Austin Clements.

Signed-off-by: Justus Winter &lt;4winter@informatik.uni-hamburg.de&gt;
</content>
</entry>
<entry>
<title>Convert non-UTF-8 parts to UTF-8 before indexing them</title>
<updated>2012-02-29T11:41:39Z</updated>
<author>
<name>Michal Sojka</name>
<email>sojkam1@fel.cvut.cz</email>
</author>
<published>2012-02-24T07:36:22Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=40edc971a82e236704216058591d4c7684f8058f'/>
<id>urn:sha1:40edc971a82e236704216058591d4c7684f8058f</id>
<content type='text'>
This fixes a bug that didn't allow to search for non-ASCII words such
parts. The code here was copied from show_text_part_content(), because
the show command already does the needed conversion when showing the
message.
</content>
</entry>
<entry>
<title>Prevent segmentation fault in notmuch_database_close</title>
<updated>2012-02-21T03:03:25Z</updated>
<author>
<name>Justus Winter</name>
<email>4winter@informatik.uni-hamburg.de</email>
</author>
<published>2012-02-18T23:56:57Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=e2e95caa51f8c1ea57b4fc7d3926fda1fb1aed10'/>
<id>urn:sha1:e2e95caa51f8c1ea57b4fc7d3926fda1fb1aed10</id>
<content type='text'>
Previously opening a notmuch database in read write mode that has been
locked resulted in the notmuch_database_open function executing
notmuch_database_close as a cleanup function. notmuch_database_close
failed to check whether the xapian database has in fact been created.

Add a check whether the xapian database object has actually been
created before trying to call its flush method.

Signed-off-by: Justus Winter &lt;4winter@informatik.uni-hamburg.de&gt;
</content>
</entry>
<entry>
<title>lib: Use talloc to simplify cleanup in notmuch_database_open</title>
<updated>2012-02-04T01:15:45Z</updated>
<author>
<name>Austin Clements</name>
<email>amdragon@MIT.EDU</email>
</author>
<published>2012-01-29T05:50:10Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=c32116d04807eec475d7e19bb6723c35bc399059'/>
<id>urn:sha1:c32116d04807eec475d7e19bb6723c35bc399059</id>
<content type='text'>
Previously, we manually "free"d various pointers in
notmuch_database_open.  Use a local talloc context instead to simplify
cleanup and eliminate various NULL pointer initializations and
conditionals.
</content>
</entry>
<entry>
<title>lib: Release resources if notmuch_database_open fails</title>
<updated>2012-02-04T01:15:26Z</updated>
<author>
<name>Austin Clements</name>
<email>amdragon@MIT.EDU</email>
</author>
<published>2012-01-29T05:50:09Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=6c0adab23eadb81bb1254f4b82175902df11bb3f'/>
<id>urn:sha1:6c0adab23eadb81bb1254f4b82175902df11bb3f</id>
<content type='text'>
Previously, if a Xapian exception occurred in notmuch_database_open,
we failed to clean up the allocated notmuch_database_t object.
</content>
</entry>
<entry>
<title>lib: Don't delete uninitialized pointers</title>
<updated>2012-02-04T01:14:59Z</updated>
<author>
<name>Austin Clements</name>
<email>amdragon@MIT.EDU</email>
</author>
<published>2012-01-29T05:50:08Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=a8ee1c75c348f41d88398fc394812e66e8e8b72e'/>
<id>urn:sha1:a8ee1c75c348f41d88398fc394812e66e8e8b72e</id>
<content type='text'>
In the error-handling paths of notmuch_database_open, we call
notmuch_database_close, which "delete"s several objects referenced by
the notmuch_database_t object.  However, some of these pointers may be
uninitialized, resulting in undefined behavior.  Hence, allocate the
notmuch_database_t with talloc_zero to make sure these pointers are
NULL so that "delete"ing them is harmless.
</content>
</entry>
<entry>
<title>lib: Add support for automatically excluding tags from queries</title>
<updated>2012-01-17T01:06:35Z</updated>
<author>
<name>Austin Clements</name>
<email>amdragon@MIT.EDU</email>
</author>
<published>2012-01-15T00:17:33Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=3b76adf9e2c026dd03b820f4c6eab50e25444113'/>
<id>urn:sha1:3b76adf9e2c026dd03b820f4c6eab50e25444113</id>
<content type='text'>
This is useful for tags like "deleted" and "spam" that people
generally want to exclude from query results.  These exclusions will
be overridden if a tag is explicitly mentioned in a query.
</content>
</entry>
<entry>
<title>lib: fix messages.c build warn</title>
<updated>2012-01-10T10:33:23Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani@nikula.org</email>
</author>
<published>2012-01-07T23:26:17Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=3f9d73884ee7c26797a1528b89e1fe63aadc3271'/>
<id>urn:sha1:3f9d73884ee7c26797a1528b89e1fe63aadc3271</id>
<content type='text'>
lib/messages.c: In function ‘notmuch_messages_move_to_next’:
lib/messages.c:131:2: warning: ISO C forbids ‘return’ with expression, in function returning void [-pedantic]

Signed-off-by: Jani Nikula &lt;jani@nikula.org&gt;
</content>
</entry>
<entry>
<title>lib: call g_mime_init() from notmuch_database_open()</title>
<updated>2012-01-01T03:08:15Z</updated>
<author>
<name>Kazuo Teramoto</name>
<email>kaz.rag@gmail.com</email>
</author>
<published>2011-12-31T04:37:41Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=442d405ad301bd0bc9dc1d385c21f943ba743308'/>
<id>urn:sha1:442d405ad301bd0bc9dc1d385c21f943ba743308</id>
<content type='text'>
As reported in
id:"CAEbOPGyuHnz4BPtDutnTPUHcP3eYcRCRkXhYoJR43RUMw671+g@mail.gmail.com"
sometimes gmime tries to access a NULL pointer, e.g. g_mime_iconv_open()
tries to access iconv_cache that is NULL if g_mime_init() is not called.
This causes notmuch to segfault when calling gmime functions.

Calling g_mime_init() initializes iconv_cache and others variables needed
by gmime, making sure they are initialized when notmuch calls gmime
functions.

Test marked fix by db.
</content>
</entry>
</feed>
