From: michael+sup@stapelberg.de (Michael Stapelberg)
Subject: [sup-talk] Validating GPG keys in parallel and in background
Date: Fri, 10 Jul 2009 22:19:14 +0200 [thread overview]
Message-ID: <1247256988-sup-2799@x200> (raw)
Hi,
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.
This is especially important for big mailing lists (like debian-devel) which
contain many signed mails.
Best regards,
Michael
next reply other threads:[~2009-07-10 20:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-10 20:19 Michael Stapelberg [this message]
2009-07-27 17:24 ` William Morgan
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=1247256988-sup-2799@x200 \
--to=michael+sup@stapelberg.de \
/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