From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] Validating GPG keys in parallel and in background
Date: Mon, 27 Jul 2009 10:24:09 -0700 [thread overview]
Message-ID: <1248715421-sup-9481@masanjin.net> (raw)
In-Reply-To: <1247256988-sup-2799@x200>
Reformatted excerpts from Michael Stapelberg's message of 2009-07-10:
> it seems like sup is blocking during the validation of GPG
> signed/encrypted mails. While for encryption it makes some sense to
> block, for signed mails it would be better to just display the message
> and add the information about the signature status later. The same
> approach could be used for encrypted messages: Display "decrypting..."
> and update it when done.
I agree. This would be great.
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2009-07-27 17:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-10 20:19 Michael Stapelberg
2009-07-27 17:24 ` William Morgan [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1248715421-sup-9481@masanjin.net \
--to=wmorgan-sup@masanjin.net \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox