Re: Refactoring of mml1991.el, mml2015.el, mml-smime.el

[Daiki Ueno <ueno@gnu.org>]

Jens Lechtenboerger <jens.lechtenboerger@fsfe.org> writes:

> Yes, I can move that to mml-sec.el.  However, note that I’m not
> restricting functionality to pgpmime.  Inline PGP is still available
> (via mml1991.el).  The variables whose names include “openpgp” in my
> code cover pgpmime (mml2015.el) as well as inline PGP (mml1991.el).
> Therefore, I’d like to use “openpgp” instead of “pgpmime”.

Right, then "openpgp" would be fine.

> Moreover, in mml-sec.el the variables mml-secure-cache-passphrase
> and mml-secure-passphrase-cache-expiry are defined, which have
> specialized versions in mml-smime.el, mml1991.el, and mml2015.el,
> which I meant to delete or to supersede by two new variables (for
> OpenPGP and S/MIME).  So far, I didn’t receive strong feedback on
> the related issue of my e-mail (passphrase caching in Emacs vs
> gpg-agent).  Now I wonder whether to get rid of all of them except
> those in mml-secure.el (with a recommendation to use gpg-agent).

It's tempting to remove them, but I guess we still need to care users
who keep using gpg1 without gpg-agent.

> How should I proceed from here?  Ask for opinions on other mailing
> lists such as the following two?
> https://lists.gnu.org/mailman/listinfo/info-gnus-english
> https://lists.gnu.org/mailman/listinfo/help-gnu-emacs

If there is any incompatible change in the patch, then it would be good
to announce on those lists.  On the other hand, if you are doing only
refactoring, I doubt it will be useful to ask on the lists and it might
be easier to directly push the changes to the git repo and gather
practical feedbacks.

Do you have copyright assignment for Emacs?  If not, consider filing
one.  Once the process has done, I think you can ask Lars or Ted for the
commit access.

Regards,
-- 
Daiki Ueno