From: Uwe Brauer <oub@mat.ucm.es>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Teemu Likonen <tlikonen@iki.fi>, 37025@debbugs.gnu.org, oub@mat.ucm.es
Subject: bug#37025: [found the culprit]
Date: Mon, 26 Aug 2019 08:57:58 +0200 [thread overview]
Message-ID: <87h864beh5.fsf@mat.ucm.es> (raw)
In-Reply-To: <87r2585v64.fsf@gnus.org>
[-- Attachment #1: Type: text/plain, Size: 731 bytes --]
>>> "LI" == Lars Ingebrigtsen <larsi@gnus.org> writes:
> Teemu Likonen <tlikonen@iki.fi> writes:
>> The code is probably clearer if we define a separate predicate function
>> for checking GnuPG version. I made another version of the patch which
>> defines function epg-required-version-p (epg-config.el) and uses the
>> function in epg.el. The function is used twice in my patch but it can be
>> useful in the future.
> Looks good to me; I've now applied it to the trunk. Uwe, can you
> confirm that this fixes the problem you were seeing?
Let me pull and check. I presume these are commits
42ba6200af10c00c72ac13912d6fb42a7af88058
and
f5fa0c9062d065dc61fdff92b56b9f5da439a83d
Uwe
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5025 bytes --]
next prev parent reply other threads:[~2019-08-26 6:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-14 10:24 bug#37025: 27.0.50; smime signing and encryption does not work any longer Uwe Brauer
2019-08-14 18:54 ` bug#37025: [found the culprit] (was: bug#37025: 27.0.50; smime signing and encryption does not work any longer) Uwe Brauer
2019-08-14 19:14 ` Teemu Likonen
2019-08-15 1:39 ` bug#37025: [found the culprit] Glenn Morris
2019-08-15 4:48 ` Teemu Likonen
2019-08-15 7:38 ` Uwe Brauer
2019-08-15 16:08 ` Teemu Likonen
2019-08-15 16:12 ` Uwe Brauer
2019-08-18 15:13 ` Teemu Likonen
2019-08-26 5:53 ` Lars Ingebrigtsen
2019-08-26 6:57 ` Uwe Brauer [this message]
2019-08-26 7:31 ` bug#37025: [confirmed] (was: bug#37025: [found the culprit]) Uwe Brauer
2019-08-26 14:44 ` Teemu Likonen
2019-08-27 6:43 ` bug#37025: [confirmed] Lars Ingebrigtsen
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=87h864beh5.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--cc=37025@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=tlikonen@iki.fi \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.