From: Simon Josefsson <jas@extundo.com>
Subject: Re: two versions of starttls.el?
Date: Thu, 27 May 2004 09:19:19 +0200 [thread overview]
Message-ID: <ilu4qq2s5fs.fsf@latte.josefsson.org> (raw)
In-Reply-To: <874qq2ao9w.fsf@tc-1-100.kawasaki.gol.ne.jp>
Miles Bader <miles@gnu.org> writes:
> So now that there's a "merged" version of starttls.el (in contrib/), is
> there any point to keeping the old version in lisp/? The situation
> seemed confusing enough before, but now it's even weirder; why not just
> put the merged version in lisp/ and get rid of all other versions?
Sounds right. I forgot about the copy in lisp/. I've done what you
propose, thanks.
Btw, I'd appreciate if people using STARTTLS would try to install
GNUTLS (0.9.90 or later) and do (setq starttls-use-gnutls t) to test
the new GNUTLS support in starttls.el.
Note! There should be NO change in behaviour resulting from this
patch, unless you toggle that variable. If something stops working,
pleas tell me.
For more information, see:
http://article.gmane.org/gmane.emacs.devel/23967
prev parent reply other threads:[~2004-05-27 7:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-26 21:09 Miles Bader
2004-05-27 7:19 ` Simon Josefsson [this message]
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=ilu4qq2s5fs.fsf@latte.josefsson.org \
--to=jas@extundo.com \
/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).