From: Jameson Graef Rollins <jrollins@finestructure.net>
To: Jani Nikula <jani@nikula.org>, Austin Clements <amdragon@MIT.EDU>
Cc: Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: [PATCH v5 0/7] cli: improved crypto internals
Date: Sun, 10 Jun 2012 22:41:48 -0700 [thread overview]
Message-ID: <87zk8a2yn7.fsf@servo.finestructure.net> (raw)
In-Reply-To: <874nqjq7ue.fsf@nikula.org>
[-- Attachment #1: Type: text/plain, Size: 270 bytes --]
On Sun, Jun 10 2012, Jani Nikula <jani@nikula.org> wrote:
> On Sun, 10 Jun 2012, Austin Clements <amdragon@MIT.EDU> wrote:
>> LGTM. Sorry for dropping the ball on reviewing this final version.
>
> Ditto, for both.
Thank you guys both for the thorough reviews.
jamie.
[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]
next prev parent reply other threads:[~2012-06-11 5:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-26 18:45 [PATCH v5 0/7] cli: improved crypto internals Jameson Graef Rollins
2012-05-26 18:45 ` [PATCH v5 1/7] cli: use new typedef to deal with gmime 2.4/2.6 context incompatibility Jameson Graef Rollins
2012-05-26 18:45 ` [PATCH v5 2/7] cli: new crypto structure to store crypto contexts and parameters, and functions to support it Jameson Graef Rollins
2012-05-26 18:45 ` [PATCH v5 3/7] cli: modify show and reply to use new crypto struct Jameson Graef Rollins
2012-05-26 18:45 ` [PATCH v5 4/7] cli: modify mime_node_open to take new crypto struct as argument Jameson Graef Rollins
2012-05-26 18:45 ` [PATCH v5 5/7] cli: modify mime_node_context to use the new crypto struct Jameson Graef Rollins
2012-05-26 18:45 ` [PATCH v5 6/7] cli: new crypto verify flag to handle verification Jameson Graef Rollins
2012-05-26 18:45 ` [PATCH v5 7/7] cli: use new notmuch_crypto_get_context in mime-node.c Jameson Graef Rollins
2012-06-08 18:05 ` [PATCH v5 0/7] cli: improved crypto internals Jameson Graef Rollins
2012-06-10 2:17 ` Austin Clements
2012-06-10 19:34 ` Jani Nikula
2012-06-11 5:41 ` Jameson Graef Rollins [this message]
2012-06-10 23:20 ` David Bremner
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=87zk8a2yn7.fsf@servo.finestructure.net \
--to=jrollins@finestructure.net \
--cc=amdragon@MIT.EDU \
--cc=jani@nikula.org \
--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).