From: Jameson Graef Rollins <jrollins@finestructure.net>
To: Notmuch Mail <notmuch@notmuchmail.org>
Subject: [PATCH v2 0/5] cli: improve handling of crypto parameters and contexts
Date: Fri, 18 May 2012 10:32:32 -0700 [thread overview]
Message-ID: <1337362357-31281-1-git-send-email-jrollins@finestructure.net> (raw)
Here's a second version of this series [0]. I think I have addressed
most of Austin's and Jani's comments.
I've tried to make a compromise between Jani's desire to not see any
unneeded initialization and my desire to have clarity and to make
defaults that define behavior explicit. I ended up only initializing
the variables that define default user behavior. I hope that's ok.
jamie.
[0] id:"1337205359-2444-1-git-send-email-jrollins@finestructure.net"
next reply other threads:[~2012-05-18 17:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-18 17:32 Jameson Graef Rollins [this message]
2012-05-18 17:32 ` [PATCH v2 1/5] cli: new crypto structure to store crypto contexts and parameters Jameson Graef Rollins
2012-05-18 17:32 ` [PATCH v2 2/5] cli: modify mime_node_open to take crypto struct as argument Jameson Graef Rollins
2012-05-18 17:32 ` [PATCH v2 3/5] cli: modify mime_node_context to use the new notmuch_crypto_t Jameson Graef Rollins
2012-05-18 17:32 ` [PATCH v2 4/5] cli: new crypto verify flag to handle verification Jameson Graef Rollins
2012-05-18 17:32 ` [PATCH v2 5/5] cli: lazily create the crypto gpg context only when needed Jameson Graef Rollins
2012-05-18 19:21 ` Austin Clements
2012-05-18 19:45 ` Jameson Graef Rollins
2012-05-18 20:37 ` Daniel Kahn Gillmor
2012-05-18 20:42 ` Jameson Graef Rollins
2012-05-19 11:26 ` [PATCH v2 4/5] cli: new crypto verify flag to handle verification Jani Nikula
2012-05-19 16:28 ` Jameson Graef Rollins
2012-05-18 19:09 ` [PATCH v2 3/5] cli: modify mime_node_context to use the new notmuch_crypto_t Austin Clements
2012-05-18 19:17 ` Jameson Graef Rollins
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=1337362357-31281-1-git-send-email-jrollins@finestructure.net \
--to=jrollins@finestructure.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).