From: Uwe Brauer <oub@mat.ucm.es>
To: emacs-devel@gnu.org
Subject: Re: bug#37025: 27.0.50; smime signing and encryption does not work any longer
Date: Sun, 18 Aug 2019 14:29:48 +0200 [thread overview]
Message-ID: <878srqodvn.fsf@mat.ucm.es> (raw)
In-Reply-To: 837e7eqxms.fsf@gnu.org
[-- Attachment #1: Type: text/plain, Size: 840 bytes --]
> Indeed. And there's no need to split that discussion into 2 mailing
> lists. Those who are relevant to making the decision about the fix
> read the bug list anyway.
Ok.
> Two comments (1) please wait for at least a few days before deciding
> that the matter stalled and needs to be expedited, let alone in
> another list; and (2) I personally didn't get the impression that the
> proposed fix is final and/or agreed upon, due to the issue with the
> version of gpg.
There was a second patch which checked the pgp version. However it is
not clear to me what was agreed on. So what is the general polics in
such a case. A change was introduced, which presented a bug for some use
case, a fix was not agreed or applied.
So shouldn't that commit not be removed, at least temporally, till a fix
is agreed upon?
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5025 bytes --]
next prev parent reply other threads:[~2019-08-18 12:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-15 7:53 bug#37025: 27.0.50; smime signing and encryption does not work any longer Uwe Brauer
2019-08-15 15:03 ` Eli Zaretskii
2019-08-18 12:29 ` Uwe Brauer [this message]
2019-08-18 14:23 ` Eli Zaretskii
2019-08-18 15:14 ` Teemu Likonen
-- strict thread matches above, loose matches on Subject: below --
2019-08-14 10:24 Uwe Brauer
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=878srqodvn.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--cc=emacs-devel@gnu.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 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.