From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: Use rfc2015.el?
Date: 28 Aug 2000 22:09:01 -0400 [thread overview]
Message-ID: <2nbsyclsxu.fsf@tiger.jia.vnet> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "27 Aug 2000 14:16:46 +0200"
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> Any suggestions? What would be a good way to get at the most recent
> stable version of the file? Maybe rfc2015.el could be moved out of
> contrib into the distribution?
There is no more recent stable version of the file. I don't think it
will be moved to the distribution soon. Currently, it still can not
verify signatures. I have to hack some Gnus codes to get it work. It
won't be done in near future.
Also, I might rewrite some code to support multiple signatures. Any
thoughts?
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> Is it possible to use rfc2015.el together with GPG? What does one
> have to do?
It uses mailcrypt. mailcrypt supports GPG, so does it.
ShengHuo
next prev parent reply other threads:[~2000-08-29 2:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-27 12:16 Kai Großjohann
2000-08-28 10:15 ` Kai Großjohann
2000-08-29 2:09 ` ShengHuo ZHU [this message]
2000-08-29 8:07 ` Kai Großjohann
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=2nbsyclsxu.fsf@tiger.jia.vnet \
--to=zsh@cs.rochester.edu \
/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).