Gnus development mailing list
 help / color / mirror / Atom feed
From: Daiki Ueno <ueno@gnu.org>
To: =?iso-2022-jp-2?B?GyQoRCkoGyhCdWthc3o=?= Stelmach
	<lukasz.stelmach@iem.pw.edu.pl>
Cc: ding@gnus.org
Subject: Re: [BUG] mml2015-epg-find-usable-key finds unusable key
Date: Fri, 15 Feb 2013 18:14:19 +0900	[thread overview]
Message-ID: <m3ip5uym50.fsf-ueno@gnu.org> (raw)
In-Reply-To: <87haleovnf.fsf%lukasz.stelmach@iem.pw.edu.pl> (=?iso-2022-jp-2?B?IhskKEQpKBsoQnVrYXN6?= Stelmach"'s message of "Fri, 15 Feb 2013 08:59:00 +0100")

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=iso-2022-jp-2, Size: 578 bytes --]

^[$(D)(^[(Bukasz Stelmach <lukasz.stelmach@iem.pw.edu.pl> writes:

> The patch looks reasonable (-; I'll check tooday in the evening
> (CET). Before applying please follow the discussion (if it appears) on
> the gpg-devel mailing list:
>
> http://permalink.gmane.org/gmane.comp.encryption.gpg.devel/17572 

I remember that the GPG author originally suggested the current code ;-)
http://thread.gmane.org/gmane.emacs.gnus.general/64349

But let's see how it goes.  Perhaps some built-in key filtering feature
in GPG (or GPGME) might be generally useful.

Regards,
-- 
Daiki Ueno



  reply	other threads:[~2013-02-15  9:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-13 19:55 Łukasz Stelmach
2013-02-14 19:28 ` Łukasz Stelmach
2013-02-15  4:05 ` Daiki Ueno
2013-02-15  7:59   ` Łukasz Stelmach
2013-02-15  9:14     ` Daiki Ueno [this message]
2013-02-16 18:35   ` Łukasz Stelmach
2013-02-16 21:11     ` Łukasz Stelmach
2013-02-17  3:12       ` Daiki Ueno
2013-02-17  7:47         ` Łukasz Stelmach
2013-02-17  9:02           ` Daiki Ueno
2013-02-17 10:20             ` Daiki Ueno
2013-02-17 21:29               ` Łukasz Stelmach

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=m3ip5uym50.fsf-ueno@gnu.org \
    --to=ueno@gnu.org \
    --cc=ding@gnus.org \
    --cc=lukasz.stelmach@iem.pw.edu.pl \
    /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;
as well as URLs for NNTP newsgroup(s).