unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Jameson Graef Rollins <jrollins@finestructure.net>
To: Jani Nikula <jani@nikula.org>, notmuch@notmuchmail.org
Subject: Re: [PATCH] man: show and reply --decrypt option requires gpg-agent
Date: Fri, 01 Mar 2013 08:56:49 -0800	[thread overview]
Message-ID: <87fw0foy7i.fsf@servo.finestructure.net> (raw)
In-Reply-To: <1362156206-19481-1-git-send-email-jani@nikula.org>

[-- Attachment #1: Type: text/plain, Size: 2001 bytes --]

On Fri, Mar 01 2013, Jani Nikula <jani@nikula.org> wrote:
> ---
>  man/man1/notmuch-reply.1 |    9 ++++++---
>  man/man1/notmuch-show.1  |    9 +++++++--
>  2 files changed, 13 insertions(+), 5 deletions(-)
>
> diff --git a/man/man1/notmuch-reply.1 b/man/man1/notmuch-reply.1
> index 454bdee..bf2021f 100644
> --- a/man/man1/notmuch-reply.1
> +++ b/man/man1/notmuch-reply.1
> @@ -89,9 +89,12 @@ user's addresses.
>  
>  Decrypt any MIME encrypted parts found in the selected content
>  (ie. "multipart/encrypted" parts). Status of the decryption will be
> -reported (currently only supported with --format=json and --format=sexp)
> -and the multipart/encrypted part will be replaced by the decrypted
> -content.
> +reported (currently only supported with --format=json and
> +--format=sexp) and on successful decryption the multipart/encrypted
> +part will be replaced by the decrypted content.
> +
> +Decryption expects a functioning \fBgpg-agent\fR(1) to provide any
> +needed credentials. Without one, the decryption will fail.
>  .RE
>  
>  See \fBnotmuch-search-terms\fR(7)
> diff --git a/man/man1/notmuch-show.1 b/man/man1/notmuch-show.1
> index 8be9eae..7697dfc 100644
> --- a/man/man1/notmuch-show.1
> +++ b/man/man1/notmuch-show.1
> @@ -163,8 +163,13 @@ will be replaced by the signed data.
>  Decrypt any MIME encrypted parts found in the selected content
>  (ie. "multipart/encrypted" parts). Status of the decryption will be
>  reported (currently only supported with --format=json and
> ---format=sexp) and the multipart/encrypted part will be replaced
> -by the decrypted content.  Implies --verify.
> +--format=sexp) and on successful decryption the multipart/encrypted
> +part will be replaced by the decrypted content.
> +
> +Decryption expects a functioning \fBgpg-agent\fR(1) to provide any
> +needed credentials. Without one, the decryption will fail.
> +
> +Implies --verify.
>  .RE
>  
>  .RS 4
> -- 
> 1.7.10.4

LGTM.

jamie.

[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]

  reply	other threads:[~2013-03-01 16:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-27  7:40 [PATCH] cli: crypto: tell gmime to use gpg-agent Jani Nikula
2013-02-27  8:45 ` Tomi Ollila
2013-02-27 16:14 ` Jameson Graef Rollins
2013-02-27 17:11   ` David Bremner
2013-02-27 17:25     ` Jameson Graef Rollins
2013-02-27 22:46       ` Jani Nikula
2013-03-01  0:10         ` Jameson Graef Rollins
2013-03-01  6:12           ` Daniel Kahn Gillmor
2013-03-01  6:52             ` Tomi Ollila
2013-03-01 16:43 ` [PATCH] man: show and reply --decrypt option requires gpg-agent Jani Nikula
2013-03-01 16:56   ` Jameson Graef Rollins [this message]
2013-03-02 14:48 ` [PATCH] cli: crypto: tell gmime to use gpg-agent 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=87fw0foy7i.fsf@servo.finestructure.net \
    --to=jrollins@finestructure.net \
    --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).