<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/contrib, branch debian/0.26.2-2</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=debian%2F0.26.2-2</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=debian%2F0.26.2-2'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2017-08-23T10:38:37Z</updated>
<entry>
<title>database: add n_d_index_file (deprecates n_d_add_message)</title>
<updated>2017-08-23T10:38:37Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2017-08-17T23:14:25Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=b10ce6bc23002d48916b1b2f375480e7540e3164'/>
<id>urn:sha1:b10ce6bc23002d48916b1b2f375480e7540e3164</id>
<content type='text'>
We need a way to pass parameters to the indexing functionality on the
first index, not just on reindexing.  The obvious place is in
notmuch_database_add_message.  But since modifying the argument list
would break both API and ABI, we needed a new name.

I considered notmuch_database_add_message_with_params(), but the
functionality we're talking about doesn't always add a message.  It
tries to index a specific file, possibly adding a message, but
possibly doing other things, like adding terms to an existing message,
or failing to deal with message objects entirely (e.g. because the
file didn't contain a message).

So i chose the function name notmuch_database_index_file.

I confess i'm a little concerned about confusing future notmuch
developers with the new name, since we already have a private
_notmuch_message_index_file function, and the two do rather different
things.  But i think the added clarity for people linking against the
future libnotmuch and the capacity for using index parameters makes
this a worthwhile tradeoff.  (that said, if anyone has another name
that they strongly prefer, i'd be happy to go with it)

This changeset also adjusts the tests so that we test whether the new,
preferred function returns bad values (since the deprecated function
just calls the new one).

We can keep the deprecated n_d_add_message function around as long as
we like, but at the next place where we're forced to break API or ABI
we can probably choose to drop the name relatively safely.

NOTE: there is probably more cleanup to do in the ruby and go bindings
to complete the deprecation directly.  I don't know those languages
well enough to attempt a fix; i don't know how to test them; and i
don't know the culture around those languages about API additions or
deprecations.
</content>
</entry>
<entry>
<title>Use rooted paths in .gitignore files</title>
<updated>2017-08-18T22:42:35Z</updated>
<author>
<name>Vladimir Panteleev</name>
<email>notmuch@thecybershadow.net</email>
</author>
<published>2017-08-17T00:41:10Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=ca4688e103c644fa383108a79668e8e0b4dbe262'/>
<id>urn:sha1:ca4688e103c644fa383108a79668e8e0b4dbe262</id>
<content type='text'>
A leading / in paths in a .gitignore file matches the beginning of the
path, meaning that for patterns without slashes, git will match files
only in the current directory as opposed to in any subdirectory.

Prefix relevant paths with / in .gitignore files, to prevent
accidentally ignoring files in subdirectories and possibly slightly
improve the performance of "git status".
</content>
</entry>
<entry>
<title>fixed wrong constant values</title>
<updated>2016-09-03T23:15:46Z</updated>
<author>
<name>laochailan</name>
<email>laochailan@web.de</email>
</author>
<published>2015-05-31T12:02:12Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=a26b06f09dd2317ab8ffb76dcc1ebb64ff2a80ad'/>
<id>urn:sha1:a26b06f09dd2317ab8ffb76dcc1ebb64ff2a80ad</id>
<content type='text'>
before, they were both zero, so getting a read-writeable handle was
impossible.
</content>
</entry>
<entry>
<title>Added thread bindings to go bindings</title>
<updated>2016-09-03T23:15:16Z</updated>
<author>
<name>laochailan</name>
<email>laochailan@web.de</email>
</author>
<published>2015-05-31T12:02:11Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=263a690ac47ced487a7305bd5056723662d1c28c'/>
<id>urn:sha1:263a690ac47ced487a7305bd5056723662d1c28c</id>
<content type='text'>
</content>
</entry>
<entry>
<title>bindings: move go bindings to contrib</title>
<updated>2016-09-03T23:13:08Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2016-08-23T23:50:05Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=b0d03fc5ba1211ed783a5c052d01407d95c8446f'/>
<id>urn:sha1:b0d03fc5ba1211ed783a5c052d01407d95c8446f</id>
<content type='text'>
This signals two things, an intent to be more liberal about accepting
patches, and an intent to stop distributing the bindings if maintenance
doesn't pick up.
</content>
</entry>
<entry>
<title>contrib: remove old copy of vim front end</title>
<updated>2016-09-03T23:10:01Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2016-08-23T23:40:51Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=2f2df00d436b117acd3e0de13548406efaf272b8'/>
<id>urn:sha1:2f2df00d436b117acd3e0de13548406efaf272b8</id>
<content type='text'>
Having two in the tree is just confusing. And the viml one is even more
out of date than the ruby one.
</content>
</entry>
<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>notmuch-mutt: use env to locate perl for increased portability</title>
<updated>2016-04-30T10:34:00Z</updated>
<author>
<name>Stefano Zacchiroli</name>
<email>zack@upsilon.cc</email>
</author>
<published>2016-04-21T18:10:25Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=e3e03fb718de9790bc9b7a78210f42559bff24e5'/>
<id>urn:sha1:e3e03fb718de9790bc9b7a78210f42559bff24e5</id>
<content type='text'>
Note: this patch drops -w from the shebang line, but we still have
"use warnings" in the script, which is superior anyhow.

Thanks Andreas Tolfsen for the suggestion.
</content>
</entry>
<entry>
<title>notmuch-mutt: fix xargs/ln usage for OpenBSD compatibility</title>
<updated>2015-05-04T06:04:38Z</updated>
<author>
<name>Jack Peirce</name>
<email>JPeirce@sourcecode.com</email>
</author>
<published>2015-05-01T08:32:05Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=1ad02d06b52fce6ab828ebefca9bdbfc269e9360'/>
<id>urn:sha1:1ad02d06b52fce6ab828ebefca9bdbfc269e9360</id>
<content type='text'>
- xargs: use -r flag instead of --no-run-if-empty
- ln: use -I flag/3rd form of ln command instead of -t flag/4th form

Signed-off-by: Stefano Zacchiroli &lt;zack@upsilon.cc&gt;
</content>
</entry>
<entry>
<title>notmuch-mutt: support for messages that lack Message-ID headers</title>
<updated>2015-02-16T12:58:13Z</updated>
<author>
<name>Stefano Zacchiroli</name>
<email>zack@upsilon.cc</email>
</author>
<published>2015-02-15T12:39:08Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=1722ea2c95865cb20cc2578894eca2cdaddc1d7a'/>
<id>urn:sha1:1722ea2c95865cb20cc2578894eca2cdaddc1d7a</id>
<content type='text'>
For those messages, compute a synthetic Message-ID based on the SHA1
of the whole message, in the same way that notmuch would do. See:
http://git.notmuchmail.org/git/notmuch/blob/HEAD:/lib/sha1.c

To do the above, rewrite get_message_id() to accumulate header lines,
parse them to check for Message-ID, and fallback to SHA1 computation
if it is not present.

Thanks to:
- Jan N. Klug for preliminary versions of this patch
- Tomi Ollila for suggesting an elegant implementation
</content>
</entry>
</feed>
