From: Uwe Brauer <oub@mat.ucm.es>
To: 37025@debbugs.gnu.org
Cc: Teemu Likonen <tlikonen@iki.fi>
Subject: bug#37025: [found the culprit] (was: bug#37025: 27.0.50; smime signing and encryption does not work any longer)
Date: Wed, 14 Aug 2019 20:54:47 +0200 [thread overview]
Message-ID: <8736i3y3uw.fsf@mat.ucm.es> (raw)
In-Reply-To: <87imr06o42.fsf@mat.ucm.es>
>>> "UB" == Uwe Brauer <oub@mat.ucm.es> writes:
Hi
finally I bisect and found the culprit:
git bisect good
74579d3d2bb82f300a6f2d81b7b559f0a24061db is the first bad commit
commit 74579d3d2bb82f300a6f2d81b7b559f0a24061db
Author: Teemu Likonen <tlikonen@iki.fi>
Date: Sat Jul 13 02:12:58 2019 +0200
Use the gpg --sender option
* lisp/epg.el (epg-start-encrypt)
* lisp/gnus/mml-sec.el (mml-secure-epg-encrypt): When
'mml-secure-openpgp-sign-with-sender' is non-nil message sender's
email address (in addition to its old behaviour) will also be used
to set gpg's "--sender email@domain" option.
:040000 040000 20160088e04c63a19c67d0635d3ba9248f03fd8d fa805f311eacaef3fdccee56d7286bf97059afa8 M etc
:040000 040000 87ecd6ed235d466fc9716676a621bdf8d04a6b90 8323f689077100be17ffc82bf96958e72954ed93 M lisp
This commit broke smime encoding/signing
Any comments please. @Teemu?
next prev parent reply other threads:[~2019-08-14 18:54 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 ` Uwe Brauer [this message]
2019-08-14 19:14 ` bug#37025: [found the culprit] (was: bug#37025: 27.0.50; smime signing and encryption does not work any longer) 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
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=8736i3y3uw.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--cc=37025@debbugs.gnu.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.