<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/status.c, branch release</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=release</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=release'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2020-04-13T20:14:50Z</updated>
<entry>
<title>status: add print_status_gzbytes</title>
<updated>2020-04-13T20:14:50Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2020-04-12T23:17:20Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=02112728433cb08ea2501d937a2ca3cb73a0d85b'/>
<id>urn:sha1:02112728433cb08ea2501d937a2ca3cb73a0d85b</id>
<content type='text'>
This is in the client code, rather than libnotmuch_util, because it
prints to stderr. Also it in pretends to generate notmuch status
codes.
</content>
</entry>
<entry>
<title>cli: run uncrustify</title>
<updated>2019-06-14T10:41:27Z</updated>
<author>
<name>uncrustify</name>
<email>david@tethera.net</email>
</author>
<published>2019-06-13T10:31:01Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=33382c2b5ba2537952a60ea378feff36961e4713'/>
<id>urn:sha1:33382c2b5ba2537952a60ea378feff36961e4713</id>
<content type='text'>
This is the result of running

     $ uncrustify --replace --config devel/uncrustify.cfg *.c *.h

in the top level source directory
</content>
</entry>
<entry>
<title>cli: add print_status_message()</title>
<updated>2018-05-26T14:32:14Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2018-05-11T06:57:55Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=f32e52448b8665dbf335fd97a21b49108e05a6c0'/>
<id>urn:sha1:f32e52448b8665dbf335fd97a21b49108e05a6c0</id>
<content type='text'>
This function is a parallel to print_status_query() or
print_status_database().  Thanks to David Bremner for the suggestion!
</content>
</entry>
<entry>
<title>cli/insert: return EX_TEMPFAIL for some errors</title>
<updated>2016-12-07T11:00:40Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2016-11-28T03:01:42Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=d74c5345704136611f993ca38e0d035b1da798b6'/>
<id>urn:sha1:d74c5345704136611f993ca38e0d035b1da798b6</id>
<content type='text'>
Attempt to distinguish between errors indicating misconfiguration or
programmer error, which we consider "permanent", in the sense that
automatic retries are unlikely to be useful, and those indicating
transient error conditions. We consider XAPIAN_EXCEPTION transient
because it covers the important special case of locking failure.
</content>
</entry>
<entry>
<title>CLI: add print_status_database</title>
<updated>2016-03-30T01:59:35Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2016-01-10T01:34:21Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=ccf0db161590e2aac7db0e049547c347ab4db528'/>
<id>urn:sha1:ccf0db161590e2aac7db0e049547c347ab4db528</id>
<content type='text'>
This could probably be used at quite a few places in the existing code,
but in the immediate future I plan to use in some new code in
notmuch-dump
</content>
</entry>
<entry>
<title>cli: add utility routine to print error status.</title>
<updated>2015-09-20T11:04:31Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2015-09-06T13:15:45Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=39c54df26dad01e3ec294f7c4a613d9ee71faf3e'/>
<id>urn:sha1:39c54df26dad01e3ec294f7c4a613d9ee71faf3e</id>
<content type='text'>
No attention to formatting here, initially just focus on getting the
relevant strings out of the library.
</content>
</entry>
</feed>
