<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/notmuch-show.c, branch 0.30</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.30</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.30'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2020-05-23T01:11:17Z</updated>
<entry>
<title>cli/show: If a leaf part has children, show them instead of omitting</title>
<updated>2020-05-23T01:11:17Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2020-05-12T22:29:34Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=f12fb4d819956cb467b22183f0416fed44703d0f'/>
<id>urn:sha1:f12fb4d819956cb467b22183f0416fed44703d0f</id>
<content type='text'>
Until we did PKCS#7 unwrapping, no leaf MIME part could have a child.

Now, we treat the unwrapped MIME part as the child of the PKCS#7
SignedData object.  So in that case, we want to show it instead of
deliberately omitting the content.

This fixes the test of the protected subject in
id:smime-onepart-signed@protected-headers.example.

Signed-off-by: Daniel Kahn Gillmor &lt;dkg@fifthhorseman.net&gt;
</content>
</entry>
<entry>
<title>notmuch-show.c: add an option for messages to be returned unthreaded</title>
<updated>2020-03-20T01:05:47Z</updated>
<author>
<name>Mark Walters</name>
<email>markwalters1009@gmail.com</email>
</author>
<published>2020-02-27T17:16:47Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=f140bbcb40ac2510189329c11ca8ff20650c9eab'/>
<id>urn:sha1:f140bbcb40ac2510189329c11ca8ff20650c9eab</id>
<content type='text'>
This adds a --unthreaded option to notmuch show to tell it to return
the matching messages in an unthreaded order (so just by date).

To make it easier for users, in particular for notmuch-tree.el, we
output each message with the same "nesting" as if it were an entire
thread in its own right.

amended by db: s/status= /status = /
</content>
</entry>
<entry>
<title>notmuch-show: run uncrustify</title>
<updated>2019-07-05T15:54:36Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2019-07-03T04:31:19Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=290eccc6402d53eb1ccf3d365927854104aff1ee'/>
<id>urn:sha1:290eccc6402d53eb1ccf3d365927854104aff1ee</id>
<content type='text'>
This is the result of running:

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

In the top level source directory.  I was using uncrustify
0.68.1+dfsg1-2.

I do not know why these changes were not caught in
33382c2b5ba2537952a60ea378feff36961e4713

Signed-off-by: Daniel Kahn Gillmor &lt;dkg@fifthhorseman.net&gt;
</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: replace some constructs with more uncrustify friendly ones</title>
<updated>2019-06-14T10:41:27Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2019-06-12T22:47:20Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=be8f0ba92a302798b21cf02ef73c4ad783b66cba'/>
<id>urn:sha1:be8f0ba92a302798b21cf02ef73c4ad783b66cba</id>
<content type='text'>
In particular
   - use (bool) instead of !!
   - cuddle the opening parens of function calls
   - add parens in some ternery operators
</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 payload subject instead of outside subject</title>
<updated>2019-05-29T11:05:01Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2019-05-26T22:15:58Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=1c7fbbcc99693c0433f7b06b569ce90c19ac5e1b'/>
<id>urn:sha1:1c7fbbcc99693c0433f7b06b569ce90c19ac5e1b</id>
<content type='text'>
Correctly fix the two outstanding tests so that the protected (hidden)
subject is properly reported.

Signed-off-by: Daniel Kahn Gillmor &lt;dkg@fifthhorseman.net&gt;
</content>
</entry>
<entry>
<title>cli/show: emit headers after emitting body</title>
<updated>2019-05-29T11:02:32Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2019-05-26T22:15:54Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=80728a95e6fd8bd1c4a4f8dd8040984ab5c4b04a'/>
<id>urn:sha1:80728a95e6fd8bd1c4a4f8dd8040984ab5c4b04a</id>
<content type='text'>
This paves the way for emitting protected headers after verification
and decryption, because it means that the headers will only be emitted
after the body has been parsed.

Signed-off-by: Daniel Kahn Gillmor &lt;dkg@fifthhorseman.net&gt;
</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>cli/notmuch-show: support gzipped files</title>
<updated>2019-05-03T10:48:43Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2019-03-24T03:32:44Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=103c11822ee0b7645fda6397fb40f8ac7ed9b49b'/>
<id>urn:sha1:103c11822ee0b7645fda6397fb40f8ac7ed9b49b</id>
<content type='text'>
This drops "file" from mime_node_context and just uses a local
variable. It also uses the new gzip aware utility routines recently
added to util/gmime-extra.c. The use of gzopen / gzfile in addition is
a bit icky, but the choice is between that, and providing yet another
readline implimentation that understands GMime streams.
</content>
</entry>
</feed>
