From: David Bremner <david@tethera.net>
To: David Edmondson <dme@dme.org>, notmuch@notmuchmail.org
Cc: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
Subject: Re: [PATCH v3 0/4] Retrieve GPG keys asynchronously.
Date: Tue, 03 Sep 2019 20:49:13 -0300 [thread overview]
Message-ID: <87blw1rldy.fsf@tethera.net> (raw)
In-Reply-To: <20181001160633.26775-1-dme@dme.org>
David Edmondson <dme@dme.org> writes:
> Retrieve GPG keys asynchronously.
>
> v2:
> - Update the label on buttons when they are used to request
> asyncronous key retrieval.
> - Always update the buffer when key retrieval completes, even if the
> retrieval failed, so that the label is properly re-generated.
>
> v3:
> - Code review comments from bremner:
> - Fix spelling.
> - Fix button label.
> - Update docstring to describe the redisplay conditions.
>
I went back to this series to try and do the last minor things my self,
but unfortunately I got lost in trying to do the rebase. I think it
collides with a couple of dkg's fixes (9300defd6 and 3c752b855f). If
either of you has (or can make) a version of this series that applies
cleanly to master, I'd like to get it merged (perhaps with one or two
minor tweaks that I could take care of).
d
next prev parent reply other threads:[~2019-09-03 23:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-01 16:06 [PATCH v3 0/4] Retrieve GPG keys asynchronously David Edmondson
2018-10-01 16:06 ` [PATCH v3 1/4] emacs: Asynchronous retrieval of GPG keys David Edmondson
2019-01-15 2:08 ` David Bremner
2019-01-19 11:15 ` David Edmondson
2019-01-19 12:47 ` David Bremner
2018-10-01 16:06 ` [PATCH v3 2/4] emacs: Minor refactoring of crypto code David Edmondson
2018-10-01 16:06 ` [PATCH v3 3/4] emacs: Add notmuch-crypto-gpg-program and use it David Edmondson
2018-10-01 16:06 ` [PATCH v3 4/4] emacs: Improve the reporting of key activity David Edmondson
2019-09-03 23:49 ` David Bremner [this message]
2019-09-12 1:33 ` [PATCH v3 0/4] Retrieve GPG keys asynchronously Daniel Kahn Gillmor
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=87blw1rldy.fsf@tethera.net \
--to=david@tethera.net \
--cc=dkg@fifthhorseman.net \
--cc=dme@dme.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).