<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/configure, branch 0.26_rc1</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.26_rc1</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.26_rc1'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2017-12-09T02:19:06Z</updated>
<entry>
<title>Merge branch 'release'</title>
<updated>2017-12-09T02:19:06Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2017-12-09T02:19:06Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=040c3236afcf95bead0324a48c2e0b9cd7934993'/>
<id>urn:sha1:040c3236afcf95bead0324a48c2e0b9cd7934993</id>
<content type='text'>
Conflicts:
        NEWS

Add in NEWS from point release
</content>
</entry>
<entry>
<title>crypto: signature verification reports valid User IDs</title>
<updated>2017-12-09T00:35:18Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2017-12-08T20:09:46Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=cb855d8a9d24084d0965790782c1ce04b82aa9ca'/>
<id>urn:sha1:cb855d8a9d24084d0965790782c1ce04b82aa9ca</id>
<content type='text'>
When i'm trying to understand a message signature, i care that i know
who it came from (the "validity" of the identity associated with the
key), *not* whether i'm willing to accept the keyholder's other
identity assertions (the "trust" associated with the certificate).

We've been reporting User ID information based on the "trust"
associated with the certificate, because GMime didn't clearly expose
the validity of the User IDs.

This change relies on fixes made in GMime 3.0.3 and later which
include https://github.com/jstedfast/gmime/pull/18.
</content>
</entry>
<entry>
<title>cli/help: give a hint about notmuch-emacs-mua</title>
<updated>2017-12-07T12:20:00Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2017-12-04T18:43:10Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=de80ede3dfa88d50a3a4d34cedfcd71b8bde165b'/>
<id>urn:sha1:de80ede3dfa88d50a3a4d34cedfcd71b8bde165b</id>
<content type='text'>
"notmuch help" doesn't mention "notmuch-emacs-mua" even though we
support it through the try_external_command() mechanism.

In addition, "notmuch help emacs-mua" doesn't work, even though we
ship the appropriate manpage.

This changeset fixes both of these problems.
</content>
</entry>
<entry>
<title>debian/control: build-depend on python3-sphinx instead of python-sphinx</title>
<updated>2017-12-07T12:18:29Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2017-12-06T01:46:55Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=03f4f75124c6d9882b8306873e8908aac9eee2bb'/>
<id>urn:sha1:03f4f75124c6d9882b8306873e8908aac9eee2bb</id>
<content type='text'>
python2 is going to be deprecated, and python3-sphinx is available all
the way back to oldoldstable.  let's use the more modern version.

To make this work and still ship the manpages, tell ./configure to
prefer python3 over python, if it exists.
</content>
</entry>
<entry>
<title>configure: session key handling in gmime maps to built_with("session_key")</title>
<updated>2017-12-05T01:39:50Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2017-11-30T08:59:28Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=0ff13f862cd817fc1971900a433856a2a6146e24'/>
<id>urn:sha1:0ff13f862cd817fc1971900a433856a2a6146e24</id>
<content type='text'>
This flag should make it easier to write the code for session-key
handling.

Note that this only works for GMime 2.6.21 and later (the session key
interface wasn't available before then).  It should be fine to build
the rest of notmuch if this functionality isn't available.

Note that this also adds the "session_key" built_with() aspect to
libnotmuch.
</content>
</entry>
<entry>
<title>build: don't copy the test directory for out-of-tree builds</title>
<updated>2017-10-21T19:34:55Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani@nikula.org</email>
</author>
<published>2017-09-25T20:38:39Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=d6929040a4828cf17fb1a4f4d49b95816a5e7b7c'/>
<id>urn:sha1:d6929040a4828cf17fb1a4f4d49b95816a5e7b7c</id>
<content type='text'>
It should now work without.
</content>
</entry>
<entry>
<title>build: fix unbound variable in configure</title>
<updated>2017-08-31T13:09:02Z</updated>
<author>
<name>Jan Malakhovski</name>
<email>oxij@oxij.org</email>
</author>
<published>2017-08-31T11:46:34Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=46bda291ba6b73266f6e48a539af7772a4d09edf'/>
<id>urn:sha1:46bda291ba6b73266f6e48a539af7772a4d09edf</id>
<content type='text'>
Commentary by db:

This missing initialization caused configure to crash, and hence the
build to fail in environments without cppcheck.
</content>
</entry>
<entry>
<title>build: add target to run cppcheck</title>
<updated>2017-08-30T01:05:37Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2017-08-29T11:35:26Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=af64530d3f93dd1c379ad3ba93608ca5ad700598'/>
<id>urn:sha1:af64530d3f93dd1c379ad3ba93608ca5ad700598</id>
<content type='text'>
The advantage of having a target as opposed to running cppcheck by
hand

  - reuse list of source files
  - output errors in a format parsable, e.g. by emacs
  - returns exit code 1 on any error, for possibly use in other
    targets.

For the moment, leave this as an optional target. If desired, it can
be added to e.g. the release targets in the same way as the test
target.

Using two levels of directory for the stamps is arguably
overengineering, but it doesn't really cost anything, and leaves open
the possibility of putting other kinds of stamp files there.

This only checks "new" source files (w.r.t. their last check). A future target
(cppcheck-all ?) could blow away the stamp files first.
</content>
</entry>
<entry>
<title>test: define GMime version dependant breakage</title>
<updated>2017-06-01T00:54:08Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2017-05-27T16:51:18Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=6ac3d8c27f8edc8b3b84440900771053d6efd9dd'/>
<id>urn:sha1:6ac3d8c27f8edc8b3b84440900771053d6efd9dd</id>
<content type='text'>
We have some tests where the gmime 3 behaviour seems like a bug fix,
others where it's less clear, so we allow both possibilities.
</content>
</entry>
<entry>
<title>configure: add optional support for gmime-3.0</title>
<updated>2017-06-01T00:52:15Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2017-05-27T16:51:17Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=6977316a5f6ffa4f7df8ae26963c4629740b6c9d'/>
<id>urn:sha1:6977316a5f6ffa4f7df8ae26963c4629740b6c9d</id>
<content type='text'>
This is only the changes to make configure work; it won't compile with
gmime-3.0 yet.
</content>
</entry>
</feed>
