<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/notmuch-search.c, branch debian/stretch</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=debian%2Fstretch</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=debian%2Fstretch'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2016-06-05T11:32:17Z</updated>
<entry>
<title>Use https instead of http where possible</title>
<updated>2016-06-05T11:32:17Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2016-06-02T16:26:14Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=6a833a6e83865f6999707cc30768d07e1351c2cb'/>
<id>urn:sha1:6a833a6e83865f6999707cc30768d07e1351c2cb</id>
<content type='text'>
Many of the external links found in the notmuch source can be resolved
using https instead of http.  This changeset addresses as many as i
could find, without touching the e-mail corpus or expected outputs
found in tests.
</content>
</entry>
<entry>
<title>cli: update to use new count API</title>
<updated>2015-10-05T22:51:08Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2015-09-27T15:31:58Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=e7b420a85446fa469df77e24c11f8afa06a2592e'/>
<id>urn:sha1:e7b420a85446fa469df77e24c11f8afa06a2592e</id>
<content type='text'>
Essentially replace each call to notmuch_count_* with the corresponding
_st call, followed by print_status_query.
</content>
</entry>
<entry>
<title>cli: do not sort addresses on --output=count or --deduplicate=address</title>
<updated>2015-09-26T10:41:05Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani@nikula.org</email>
</author>
<published>2015-09-03T19:40:05Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=02e394aed216622ac355ff15bae74403abf40417'/>
<id>urn:sha1:02e394aed216622ac355ff15bae74403abf40417</id>
<content type='text'>
The order of the results with --output=count and --deduplicate=address
are unspecified as they're based on a hash table traversal. This being
the case, optimize the query by explicitly requesting unsorted
results. Clarify the documentation accordingly.
</content>
</entry>
<entry>
<title>cli: add support for deduplicating based on case insensitive address</title>
<updated>2015-09-26T10:40:07Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani@nikula.org</email>
</author>
<published>2015-09-03T19:40:03Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=64b155842a87c228c45ec20fb163891695e6ccc2'/>
<id>urn:sha1:64b155842a87c228c45ec20fb163891695e6ccc2</id>
<content type='text'>
Consider all variants of an email address as one, and print the most
common variant.
</content>
</entry>
<entry>
<title>cli: change the data structure for notmuch address deduplication</title>
<updated>2015-09-26T10:37:54Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani@nikula.org</email>
</author>
<published>2015-09-25T16:48:20Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=b8f4e7da3d61733fb47111b162ccabb967a3661e'/>
<id>urn:sha1:b8f4e7da3d61733fb47111b162ccabb967a3661e</id>
<content type='text'>
Currently we key the address hash table with the case sensitive "name
&lt;address&gt;". Switch to case insensitive keying with just address, and
store the case sensitive name and address in linked lists. This will
be helpful in adding support for different deduplication schemes in
the future.

There will be a slight performance penalty for the current full case
sensitive name + address deduplication, but this is simpler as a whole
when other deduplication schemes are added, and I expect the schemes
to be added to become more popular than the current default.

Aparet from the possible performance penalty, the only user visible
change should be the change in the output ordering for
--output=count. The order is not guaranteed (and is based on hash
table traversal) currently anyway, so this should be of no
consequence.
</content>
</entry>
<entry>
<title>cli: add support for not deduplicating notmuch address results</title>
<updated>2015-09-24T10:32:24Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani@nikula.org</email>
</author>
<published>2015-09-03T19:39:59Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=e5a03354294fb9d2ddcc8c03459fc2e347bd0ec1'/>
<id>urn:sha1:e5a03354294fb9d2ddcc8c03459fc2e347bd0ec1</id>
<content type='text'>
Make it possible to use notmuch address as part of a | sort | uniq -c
pipe instead of forcing --output=count. This is useful for combining
results from multiple notmuch address queries.
</content>
</entry>
<entry>
<title>cli: convert remainder of CLI to n_q_search_{messages,threads}_st</title>
<updated>2015-09-23T11:03:34Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2015-09-06T13:15:47Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=6cdd34a4c762c954426f586d514a3e041c1db3b0'/>
<id>urn:sha1:6cdd34a4c762c954426f586d514a3e041c1db3b0</id>
<content type='text'>
I think it would be no real problem to cut and paste the gdb based
error message test from count to the other clients modified here, but
I'm not currently convinced it's worth the trouble since the code path
being tested is almost the the same, and the tests are relatively
heavyweight.
</content>
</entry>
<entry>
<title>cli: abstract new mailbox creation</title>
<updated>2015-09-07T12:43:31Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani@nikula.org</email>
</author>
<published>2015-09-03T19:39:58Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=243ca658dff5aefa2d6c76121451463360fa56a7'/>
<id>urn:sha1:243ca658dff5aefa2d6c76121451463360fa56a7</id>
<content type='text'>
We'll be needing more mailbox creation soon, so abstract it
away. While at it, check for allocation failures. No other functional
changes.
</content>
</entry>
<entry>
<title>cli: g_hash_table_lookup_extended is overkill</title>
<updated>2015-09-07T12:43:31Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani@nikula.org</email>
</author>
<published>2015-09-03T19:39:57Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=dfe15c0e1b18f4d9ab5d328399e56b3be4a251a5'/>
<id>urn:sha1:dfe15c0e1b18f4d9ab5d328399e56b3be4a251a5</id>
<content type='text'>
Switch to normal glib hash table lookup. The extended version is only
required if the values may contain NULL.
</content>
</entry>
<entry>
<title>cli: add global option "--uuid"</title>
<updated>2015-08-14T16:23:49Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2015-04-05T22:39:55Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=f76d8f82dd004cf14426a91e8a80dcd2a4b97317'/>
<id>urn:sha1:f76d8f82dd004cf14426a91e8a80dcd2a4b97317</id>
<content type='text'>
The function notmuch_exit_if_unmatched_db_uuid is split from
notmuch_process_shared_options because it needs an open notmuch
database.

There are two exceptional cases in uuid handling.

1) notmuch config and notmuch setup don't currently open the database,
   so it doesn't make sense to check the UUID.

2) notmuch compact opens the database inside the library, so we either
   need to open the database just to check uuid, or change the API.
</content>
</entry>
</feed>
