<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/lib, branch 0.3</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.3</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.3'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2010-04-27T09:02:14Z</updated>
<entry>
<title>lib: Increment library version to 1.1.0</title>
<updated>2010-04-27T09:02:14Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2010-04-27T09:02:14Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=0fb28c65f24acf8757cba12384da2d380d11f76c'/>
<id>urn:sha1:0fb28c65f24acf8757cba12384da2d380d11f76c</id>
<content type='text'>
For the addition of the new NOTMUCH_SORT_UNSORTED value.
</content>
</entry>
<entry>
<title>lib: Re-implement moving of thread authors.</title>
<updated>2010-04-27T08:48:03Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2010-04-27T08:48:03Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=c210d5632e7346b9c8582a93685747f201a27267'/>
<id>urn:sha1:c210d5632e7346b9c8582a93685747f201a27267</id>
<content type='text'>
Just before releasing 0.3 we received reports of crashes that were
bisected to the commit adding thread-author moving. Sure enough,
valgrind pointed to buffer overruns in _thread_move_matched_author.

Rather than trying to make sense of all the by strncpy, strchr, +1,
and +2 of that code, I reimplemented thread-author ordering with a
pair of hash tables and an array.

Valgrind is at least happy now on the test cases it was complaining
about previously.
</content>
</entry>
<entry>
<title>Make Received: header special in notmuch_message_file_get_header</title>
<updated>2010-04-26T21:44:06Z</updated>
<author>
<name>Dirk Hohndel</name>
<email>hohndel@infradead.org</email>
</author>
<published>2010-04-26T19:58:34Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=5b8b0377cb68904eac8fc58a933d47f605a81725'/>
<id>urn:sha1:5b8b0377cb68904eac8fc58a933d47f605a81725</id>
<content type='text'>
With this patch the Received: header becomes special in the way
we treat headers - this is the only header for which we concatenate
all the instances we find (instead of just returning the first one).

This will be used in the From guessing code for replies as we need to
be able to walk ALL of the Received: headers in a message to have a
good chance to guess which mailbox this email was delivered to.

Signed-off-by: Dirk Hohndel &lt;hohndel@infradead.org&gt;
</content>
</entry>
<entry>
<title>Simple attempt to display author names in a friendlier way</title>
<updated>2010-04-26T18:45:29Z</updated>
<author>
<name>Dirk Hohndel</name>
<email>hohndel@infradead.org</email>
</author>
<published>2010-04-24T18:20:57Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=cd19671f51b8f87303de6ab536afd6aa36efec61'/>
<id>urn:sha1:cd19671f51b8f87303de6ab536afd6aa36efec61</id>
<content type='text'>
This patch only addresses the typical Outlook/Exchange case
where we have "Last, First" &lt;first.last@company.com&gt; or
"Last, First MI" &lt;first.mi.last@company.com&gt;.

In the future we should be more fexible as to the formats
we recognize, but for now we address this one as it is the
Exchange default setting and therefore the most common one.

Signed-off-by: Dirk Hohndel &lt;hohndel@infradead.org&gt;
</content>
</entry>
<entry>
<title>Reorder displayed names of thread authors</title>
<updated>2010-04-26T18:45:00Z</updated>
<author>
<name>Dirk Hohndel</name>
<email>hohndel@infradead.org</email>
</author>
<published>2010-04-24T18:20:54Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=26d8d960ee91b55e8e4c446e08e3fc371a0acd4a'/>
<id>urn:sha1:26d8d960ee91b55e8e4c446e08e3fc371a0acd4a</id>
<content type='text'>
When displaying threads as result of a search it makes sense to list those
authors first who match the search. The matching authors are separated from the
non-matching ones with a '|' instead of a ','

Imagine the default "+inbox" query. Those mails in the thread that
match the query are actually "new" (whatever that means). And some
people seem to think that it would be much better to see those author
names first. For example, imagine a long and drawn out thread that once
was started by me; you have long read the older part of the thread and
removed the inbox tag. Whenever a new email comes in on this thread,
prior to this patch the author column in the search display will first show
"Dirk Hohndel" - I think it should first show the actual author(s) of the new
mail(s).

Signed-off-by: Dirk Hohndel &lt;hohndel@infradead.org&gt;
</content>
</entry>
<entry>
<title>Add authors member to message</title>
<updated>2010-04-26T18:44:49Z</updated>
<author>
<name>Dirk Hohndel</name>
<email>hohndel@infradead.org</email>
</author>
<published>2010-04-24T18:20:53Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=57561414d76297c16b4b6f3da570f14b4ddf020c'/>
<id>urn:sha1:57561414d76297c16b4b6f3da570f14b4ddf020c</id>
<content type='text'>
message-&gt;authors contains the author's name (as we want to print it)
get / set methods are declared in notmuch-private.h

Signed-off-by: Dirk Hohndel &lt;hohndel@infradead.org&gt;
</content>
</entry>
<entry>
<title>lib: Ensure notmuch_query_search_messages returns NULL on an exception.</title>
<updated>2010-04-24T14:27:50Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2010-04-24T14:25:12Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=138fd38afe6c6d44179952dd17c4b07e9223ad37'/>
<id>urn:sha1:138fd38afe6c6d44179952dd17c4b07e9223ad37</id>
<content type='text'>
Previously, this function may have segfaulted immediately after
reporting the exception.
</content>
</entry>
<entry>
<title>lib: Document that notmuch_query_count_messages may return 0 if an exception occurs</title>
<updated>2010-04-24T14:27:50Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2010-04-24T14:24:01Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=e3e0e26806cf95cddd4dfb11c24d1ecd15171110'/>
<id>urn:sha1:e3e0e26806cf95cddd4dfb11c24d1ecd15171110</id>
<content type='text'>
This isn't a behavioral change---just a calrification in the documentation.
</content>
</entry>
<entry>
<title>lib: Audit all notmuch_database call for Xapian exception handling.</title>
<updated>2010-04-24T14:27:50Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2010-04-24T14:22:34Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=9ef68f1444de981c47af06c948e3aa3ca5a377c8'/>
<id>urn:sha1:9ef68f1444de981c47af06c948e3aa3ca5a377c8</id>
<content type='text'>
Our current approach is for top-level entry poitns in the library
to have try/catch blocks that catch any Xapian exception and print
a message. Add a few missing blocks and fix up the documentation.
</content>
</entry>
<entry>
<title>lib: Audit calls to notmuch_message_get_header to handle NULL return</title>
<updated>2010-04-24T13:50:04Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2010-04-24T13:46:43Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=3dbef312fbe9b8da247106a177ac58d73b9b9e92'/>
<id>urn:sha1:3dbef312fbe9b8da247106a177ac58d73b9b9e92</id>
<content type='text'>
Sebastian Spaeth reported [*] a segfault within libnotmuch when
running notmuch operations while an asyncronous offlineimap job had
removed some files from the mail store. Avoid this by handling all
cases where notmuch_message_get_header could return NULL.

[*] See message id:87d3xqti3o.fsf@SSpaeth.de on notmuch@notmuchmail.org
</content>
</entry>
</feed>
