Gnus development mailing list
 help / color / mirror / Atom feed
From: Albert Krewinkel <tarleb@moltkeplatz.de>
To: Daiki Ueno <ueno@gnu.org>
Cc: ding@gnus.org
Subject: Re: [PATCH 0/2] Simpler authentication with SASL
Date: Tue, 29 Oct 2013 15:21:44 +0100	[thread overview]
Message-ID: <874n80tax3.fsf@caffelatte.moltkeplatz.de> (raw)
In-Reply-To: <m3vc0hri74.fsf-ueno@gnu.org> (Daiki Ueno's message of "Mon, 28 Oct 2013 16:02:55 +0900")

Thank you for your answer!

Daiki Ueno <ueno@gnu.org> writes:

> Thanks for the patches.  However, as sasl.el is also distributed as part
> of Emacs (under lisp/net/), you can't simply rename the API functions.

Ah yes, I should have thought of that.  Some quick searching reveals
that there are programs (e.g. the emacs jabber library) which rely on
the current SASL API.  I'm going to prepare a new patch with smaller,
non-API-breaking changes.

> Also, the 1/2 patch looks too large to review.
>
> I'd suggest to work with Emacs rather than Gnus and do the things step
> by step:
>
> (1) write unit tests so not to break the core functionality
>
> (2) refactor the code (without breaking the API), say, using
>     cl-defstruct; you can rename the constructor with :constructor
>     keyword
>
> (3) add handy helper functions e.g. sasl-authenticate

That sounds reasonable, I will follow that path.

Thanks

-- 
Albert Krewinkel
PGP: ffb8 abfa 1fd7 dbd8 b608  c980 836b e330 4b5b 9312



      reply	other threads:[~2013-10-29 14:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-26 10:54 Albert Krewinkel
2013-10-26 10:54 ` [PATCH 1/2] sasl.el: simplify authentication with SASL, make code more lispy Albert Krewinkel
2013-10-26 10:54 ` [PATCH 2/2] sieve-manage.el: adapt sieve-manage to SASL simplification Albert Krewinkel
2013-10-28  7:02 ` [PATCH 0/2] Simpler authentication with SASL Daiki Ueno
2013-10-29 14:21   ` Albert Krewinkel [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=874n80tax3.fsf@caffelatte.moltkeplatz.de \
    --to=tarleb@moltkeplatz.de \
    --cc=ding@gnus.org \
    --cc=ueno@gnu.org \
    /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).