unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Bremner <david@tethera.net>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>,
	Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: revision 3: easing access to the cryptographic envelope
Date: Sun, 26 May 2019 09:01:46 -0300	[thread overview]
Message-ID: <87zhn9l905.fsf@tethera.net> (raw)
In-Reply-To: <20190525180406.30965-1-dkg@fifthhorseman.net>

Daniel Kahn Gillmor <dkg@fifthhorseman.net> writes:

> This is the third revision of the series originally posted at
> id:20190424183113.29242-1-dkg@fifthhorseman.net (revision 2 was at
> id:20190520032228.27420-1-dkg@fifthhorseman.net)
>
> This series addresses comments raised by David Bremner in his review.
> Thanks, Bremner!

I pushed this version, with 4 minor whitespace fixups (inserted spaces
and/or deleted blank lines) that I missed in my previous review.

d

  parent reply	other threads:[~2019-05-26 12:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-25 18:04 revision 3: easing access to the cryptographic envelope Daniel Kahn Gillmor
2019-05-25 18:04 ` [PATCH v3 1/4] util/crypto: _notmuch_message_crypto: tracks message-wide crypto state Daniel Kahn Gillmor
2019-05-25 18:04 ` [PATCH v3 2/4] cli: expose message-wide crypto status from mime-node Daniel Kahn Gillmor
2019-05-25 18:04 ` [PATCH v3 3/4] mime-node: track whole-message crypto state while walking the tree Daniel Kahn Gillmor
2019-05-25 18:04 ` [PATCH v3 4/4] cli/show: emit new whole-message crypto status output Daniel Kahn Gillmor
2019-05-26 12:01 ` David Bremner [this message]
2019-05-26 15:08   ` revision 3: easing access to the cryptographic envelope Daniel Kahn Gillmor
2019-05-26 16:54     ` David Bremner
2019-05-26 22:21       ` Daniel Kahn Gillmor
2019-05-27 21:33       ` Tomi Ollila

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zhn9l905.fsf@tethera.net \
    --to=david@tethera.net \
    --cc=dkg@fifthhorseman.net \
    --cc=notmuch@notmuchmail.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://yhetil.org/notmuch.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).