Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Subject: Add elisp SASL Library?
Date: Sat, 19 Apr 2003 13:32:08 +0200	[thread overview]
Message-ID: <ilu8yu6lo3r.fsf@latte.josefsson.org> (raw)

The papers for the elisp SASL library should be solved now, but is it
too late to add the package to Gnus before 5.10?  It is IMHO nice,
modularized, code and has a texinfo manual.  The code is nicer than
the ad-hoc SASL support in imap.el.  The code has been part of XEmacs
for a while:

http://cvs.xemacs.org/viewcvs.cgi/XEmacs/packages/xemacs-packages/sasl/

The Sieve XEmacs package has been using it.

I have been running with a imap.el modified to use it for a while, and
any bugs are likely to be rather severe so people should have time to
notice them before 5.10.

So the only really experimental code are my imap.el modifications.

Should I go ahead and add it, or is it too late?




             reply	other threads:[~2003-04-19 11:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-19 11:32 Simon Josefsson [this message]
2003-04-19 18:15 ` Kai Großjohann
2003-04-27  3:17 ` Lars Magne Ingebrigtsen
2003-04-27 15:33   ` Simon Josefsson
2003-04-28  5:08     ` Lars Magne 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=ilu8yu6lo3r.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).