<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/notmuch-reply.c, branch 0.13</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.13</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.13'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2012-05-05T13:11:57Z</updated>
<entry>
<title>lib/cli: Make notmuch_database_open return a status code</title>
<updated>2012-05-05T13:11:57Z</updated>
<author>
<name>Austin Clements</name>
<email>amdragon@MIT.EDU</email>
</author>
<published>2012-04-30T16:25:33Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=5fddc07dc31481453c1af186bf7da241c00cdbf1'/>
<id>urn:sha1:5fddc07dc31481453c1af186bf7da241c00cdbf1</id>
<content type='text'>
It has been a long-standing issue that notmuch_database_open doesn't
return any indication of why it failed.  This patch changes its
prototype to return a notmuch_status_t and set an out-argument to the
database itself, like other functions that return both a status and an
object.

In the interest of atomicity, this also updates every use in the CLI
so that notmuch still compiles.  Since this patch does not update the
bindings, the Python bindings test fails.
</content>
</entry>
<entry>
<title>Use notmuch_database_destroy instead of notmuch_database_close</title>
<updated>2012-04-28T12:27:33Z</updated>
<author>
<name>Justus Winter</name>
<email>4winter@informatik.uni-hamburg.de</email>
</author>
<published>2012-04-22T12:07:53Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=6f7469f54744656f90ce215f365d5731e16acd3c'/>
<id>urn:sha1:6f7469f54744656f90ce215f365d5731e16acd3c</id>
<content type='text'>
Adapt the notmuch binaries source to the notmuch_database_close split.

Signed-off-by: Justus Winter &lt;4winter@informatik.uni-hamburg.de&gt;
</content>
</entry>
<entry>
<title>reply: Move reply citation printing to the recursive MIME walk</title>
<updated>2012-03-31T11:17:55Z</updated>
<author>
<name>Austin Clements</name>
<email>amdragon@MIT.EDU</email>
</author>
<published>2012-03-27T21:59:52Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=4ba18958b5fed52598044286e87ebb3f291e4277'/>
<id>urn:sha1:4ba18958b5fed52598044286e87ebb3f291e4277</id>
<content type='text'>
This makes more logical sense, since it makes the recursive printer
responsible for the entire reply body and lets it start at the root of
the MIME tree instead of the first child.  (We could move reply header
creation in there, too, but if we ever support proper reply to
multiple messages, we'll want just one set of reply headers computed
from the entire message set and many bodies.)
</content>
</entry>
<entry>
<title>reply: Convert default reply format to self-recursive style</title>
<updated>2012-03-31T11:17:41Z</updated>
<author>
<name>Austin Clements</name>
<email>amdragon@MIT.EDU</email>
</author>
<published>2012-03-27T21:59:51Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=4d322fb579ea66472912d10c11483844d100d17f'/>
<id>urn:sha1:4d322fb579ea66472912d10c11483844d100d17f</id>
<content type='text'>
This re-arranges the default reply formatter code to use the
mime_node_t abstraction.  There are no semantic changes.
</content>
</entry>
<entry>
<title>show/reply: Unify the code that extracts text parts</title>
<updated>2012-03-31T11:17:20Z</updated>
<author>
<name>Austin Clements</name>
<email>amdragon@MIT.EDU</email>
</author>
<published>2012-03-27T21:59:50Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=ea4fd50f45b0bc0888070125c632ea2326eb18f7'/>
<id>urn:sha1:ea4fd50f45b0bc0888070125c632ea2326eb18f7</id>
<content type='text'>
Previously, show and reply had separate implementations of decoding
and printing text parts.  Now both use show's implementation, which
was more complete.  Show's implementation has been extended with an
option to add reply quoting to the extracted part (this is implemented
as a named flag to avoid naked booleans, even though it's the only
flag it can take).
</content>
</entry>
<entry>
<title>reply: Add a JSON reply format.</title>
<updated>2012-03-20T00:53:53Z</updated>
<author>
<name>Adam Wolfe Gordon</name>
<email>awg+notmuch@xvx.ca</email>
</author>
<published>2012-03-18T16:32:36Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=1904b01b96c1b731afb9649e7b5bceffce901b88'/>
<id>urn:sha1:1904b01b96c1b731afb9649e7b5bceffce901b88</id>
<content type='text'>
This new JSON format for replies includes headers generated for a
reply message as well as the headers of the original message.  Using
this data, a client can intelligently create a reply. For example, the
emacs client will be able to create replies with quoted HTML parts by
parsing the HTML parts.
</content>
</entry>
<entry>
<title>reply: Factor out reply creation</title>
<updated>2012-03-20T00:52:54Z</updated>
<author>
<name>Adam Wolfe Gordon</name>
<email>awg+notmuch@xvx.ca</email>
</author>
<published>2012-03-18T16:32:34Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=766aebc02c3581aa6e55ce8c94ce5cbba86673c5'/>
<id>urn:sha1:766aebc02c3581aa6e55ce8c94ce5cbba86673c5</id>
<content type='text'>
Factor out the creation of a reply message based on an original
message so it can be shared by different reply formats.
</content>
</entry>
<entry>
<title>cli: use notmuch_bool_t for boolean fields in notmuch_show_params_t</title>
<updated>2012-02-12T16:58:20Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani@nikula.org</email>
</author>
<published>2012-02-06T19:57:21Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=c9c5a6f70c8371809f3b079e1aba3de3b4a13f6b'/>
<id>urn:sha1:c9c5a6f70c8371809f3b079e1aba3de3b4a13f6b</id>
<content type='text'>
Use notmuch_bool_t instead of int for entire_thread, raw, and decrypt
boolean fields in notmuch_show_params_t. No functional changes.

Signed-off-by: Jani Nikula &lt;jani@nikula.org&gt;
</content>
</entry>
<entry>
<title>show: Introduce mime_node formatter callback</title>
<updated>2012-01-25T11:21:40Z</updated>
<author>
<name>Austin Clements</name>
<email>amdragon@MIT.EDU</email>
</author>
<published>2012-01-23T23:33:10Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=7430a42e23ee775818f84ed75f417302da694152'/>
<id>urn:sha1:7430a42e23ee775818f84ed75f417302da694152</id>
<content type='text'>
This callback is the gateway to the new mime_node_t-based formatters.
This maintains backwards compatibility so the formatters can be
transitioned one at a time.  Once all formatters are converted, the
formatter structure can be reduced to only message_set_{start,sep,end}
and part, most of show_message can be deleted, and all of
show-message.c can be deleted.
</content>
</entry>
<entry>
<title>Add compatibility with gmime 2.6</title>
<updated>2012-01-21T12:52:34Z</updated>
<author>
<name>Thomas Jost</name>
<email>schnouki@schnouki.net</email>
</author>
<published>2012-01-20T09:39:24Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=00b5623d1a21d886b564d031e30749e5d02e4ae6'/>
<id>urn:sha1:00b5623d1a21d886b564d031e30749e5d02e4ae6</id>
<content type='text'>
There are lots of API changes in gmime 2.6 crypto handling. By adding
preprocessor directives, it is however possible to add gmime 2.6 compatibility
while preserving compatibility with gmime 2.4 too.

This is mostly based on id:"8762i8hrb9.fsf@bookbinder.fernseed.info".

This was tested against both gmime 2.6.4 and 2.4.31. With gmime 2.4.31, the
crypto tests all work fine (as expected). With gmime 2.6.4, one crypto test is
currently broken (signature verification with signer key unavailable), most
likely because of a bug in gmime which will hopefully be fixed in a future
version.
</content>
</entry>
</feed>
