<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/devel, branch 0.30_rc1</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.30_rc1</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.30_rc1'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2020-06-05T10:00:35Z</updated>
<entry>
<title>devel: script to calculate a list of authors.</title>
<updated>2020-06-05T10:00:35Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2020-06-03T16:05:12Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=55619625eb08f046e4e02ebc43f4aefa8903c638'/>
<id>urn:sha1:55619625eb08f046e4e02ebc43f4aefa8903c638</id>
<content type='text'>
As an initial heuristic, report anyone with at least 15 lines of code
in the current source tree. Test corpora are excluded, although
probabably this doesn't change much about the list of authors
produced.
</content>
</entry>
<entry>
<title>emacs: introduce notmuch-search-by-tag</title>
<updated>2020-04-14T15:29:31Z</updated>
<author>
<name>Keegan Carruthers-Smith</name>
<email>keegan.csmith@gmail.com</email>
</author>
<published>2020-04-13T20:10:50Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=f28e0a93379754456cf02830efcea499c6c2fc6f'/>
<id>urn:sha1:f28e0a93379754456cf02830efcea499c6c2fc6f</id>
<content type='text'>
This is like notmuch-search-filter-by-tag, but creates a new search
rather than filtering the current search. We add this to
notmuch-common-keymap since this can be used by many contexts. We bind
to the key "t", which is the same key used by
notmuch-search-filter-by-tag in notmuch-search-mode-map. This is done
intentionally since the keybinding for notmuch-search-mode-map can be
seen as a specialization of creating a new search.

This change was motivated for use in "notmuch-hello". It is a more
convenient way to search a tag than expanding the list of all tags. I
also noticed many saved searches people use are simply tags.
</content>
</entry>
<entry>
<title>nmbug: explicitly prefer python3</title>
<updated>2020-04-03T12:33:44Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2018-02-09T04:32:11Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=144cf30e2c71d57795b5fbdec10af0ef73aa01ff'/>
<id>urn:sha1:144cf30e2c71d57795b5fbdec10af0ef73aa01ff</id>
<content type='text'>
nmbug and notmuch-report are developer tools.  It's 2018, and all
developers should have python3 available.

Signed-off-by: Daniel Kahn Gillmor &lt;dkg@fifthhorseman.net&gt;
</content>
</entry>
<entry>
<title>Drop devel/printmimestructure (it is in mailscripts 0.11)</title>
<updated>2019-10-13T12:31:50Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2019-09-15T18:02:03Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=7eb9615b30274033cc0c828244569c709906c40b'/>
<id>urn:sha1:7eb9615b30274033cc0c828244569c709906c40b</id>
<content type='text'>
mailscripts 0.11 now ships a derivative of devel/printmimestructure
called email-print-mime-structure.  Maintenance for that utility will
happen in mailscripts from now on, so we should not track an
independent copy of it in notmuch's source tree.

See https://bugs.debian.org/939993 for more details about the
adoption.

Signed-off-by: Daniel Kahn Gillmor &lt;dkg@fifthhorseman.net&gt;
</content>
</entry>
<entry>
<title>uncrustify: indent classes</title>
<updated>2019-06-14T10:41:27Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2019-06-13T10:50:44Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=bcfd3e7542b3a004caba16b723c6663c7fd4b015'/>
<id>urn:sha1:bcfd3e7542b3a004caba16b723c6663c7fd4b015</id>
<content type='text'>
With previous settings member functions / variables are moved to
column 0.
</content>
</entry>
<entry>
<title>STYLE: document rules for calls, block comments, ternary ops</title>
<updated>2019-06-14T10:41:27Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2019-06-12T22:49:13Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=87df05d181976638e0b3d44d586ce4d5cfe2bd0f'/>
<id>urn:sha1:87df05d181976638e0b3d44d586ce4d5cfe2bd0f</id>
<content type='text'>
</content>
</entry>
<entry>
<title>cli/show: add information about which headers were protected</title>
<updated>2019-05-29T11:11:50Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2019-05-27T22:14:16Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=56416a54702669a23b7aa8f085a388d0c842e297'/>
<id>urn:sha1:56416a54702669a23b7aa8f085a388d0c842e297</id>
<content type='text'>
The header-mask member of the per-message crypto object allows a
clever UI frontend to mark whether a header was protected (or not).
And if it was protected, it contains enough information to show useful
detail to an interested user.  For example, an MUA could offer a "show
what this message's Subject looked like on the wire" feature in expert
mode.

As before, we only handle Subject for now, but we might be able to
handle other headers in the future.

Signed-off-by: Daniel Kahn Gillmor &lt;dkg@fifthhorseman.net&gt;

Amended by db: tweaked schemata notation.
</content>
</entry>
<entry>
<title>cli/show: emit new whole-message crypto status output</title>
<updated>2019-05-26T11:20:23Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2019-05-25T18:04:06Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=4cb789aa090fb6ba3c7897584ecbcc0a547b2f81'/>
<id>urn:sha1:4cb789aa090fb6ba3c7897584ecbcc0a547b2f81</id>
<content type='text'>
This allows MUAs that don't want to think about per-mime-part
cryptographic status to have a simple high-level overview of the
message's cryptographic state.

Sensibly structured encrypted and/or signed messages will work fine
with this.  The only requirement for the simplest encryption + signing
is that the message have all of its encryption and signing protection
(the "cryptographic envelope") in a contiguous set of MIME layers at
the very outside of the message itself.

This is because messages with some subparts signed or encrypted, but
with other subparts with no cryptographic protection is very difficult
to reason about, and even harder for the user to make sense of or work
with.

For further characterization of the Cryptographic Envelope and some of
the usability tradeoffs, see here:

   https://dkg.fifthhorseman.net/blog/e-mail-cryptography.html#cryptographic-envelope
</content>
</entry>
<entry>
<title>use #!/usr/bin/env python consistently</title>
<updated>2018-06-14T23:38:20Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2018-06-12T21:21:10Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=0741e48c3dafdc243abda866c962707344467904'/>
<id>urn:sha1:0741e48c3dafdc243abda866c962707344467904</id>
<content type='text'>
</content>
</entry>
<entry>
<title>minor cleanup to printmimestructure</title>
<updated>2018-06-14T23:36:19Z</updated>
<author>
<name>Jameson Graef Rollins</name>
<email>jrollins@finestructure.net</email>
</author>
<published>2018-06-12T21:21:09Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=0a3dff7b8a7eb0f60abd1e3f04518cce035d11ba'/>
<id>urn:sha1:0a3dff7b8a7eb0f60abd1e3f04518cce035d11ba</id>
<content type='text'>
make the source slightly easier to read.  no functional change.
</content>
</entry>
</feed>
