unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "J.P." <jp@neverwas.me>
To: Lars Ingebrigtsen <larsi@gnus.org>,
	Philip Kaludercic <philipk@posteo.net>
Cc: 57956@debbugs.gnu.org, Magnus Henoch <magnus.henoch@gmail.com>,
	emacs-erc@gnu.org
Subject: bug#57956: 29.0.50; Add minimal authorization support to sasl-scram-rfc
Date: Wed, 21 Sep 2022 06:17:27 -0700	[thread overview]
Message-ID: <87a66ssw7s.fsf__33782.132323698$1663769808$gmane$org@neverwas.me> (raw)
In-Reply-To: <87tu52awv9.fsf@gnus.org> (Lars Ingebrigtsen's message of "Tue, 20 Sep 2022 17:28:26 +0200")

Lars Ingebrigtsen <larsi@gnus.org> writes:

> "J.P." <jp@neverwas.me> writes:
>
>> Anyway, ERC would benefit greatly from these (or superior) changes
>> because we'd like to introduce `erc-compat' analogs in an upcoming
>> release (probably ERC 5.6). If anyone out there can spare the time,
>> your feedback would be greatly appreciated.
>
> Looks OK to me.

Cool, thanks.

                                * * *

Question for Philip (Cc'd):

Hi. When 29.1 is released, I might want to propose some of these updated
sasl-scram-rfc.el items for inclusion in Compat. However, one of them,

  `sasl-scram--client-final-message'

is obviously an internal function. Does that matter? Would you rather we
export it (as in rename it or alias it) beforehand (IOW, now)?

Thanks,
J.P.





  parent reply	other threads:[~2022-09-21 13:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <871qs62o0y.fsf@neverwas.me>
2022-09-20 15:28 ` bug#57956: 29.0.50; Add minimal authorization support to sasl-scram-rfc Lars Ingebrigtsen
     [not found] ` <87tu52awv9.fsf@gnus.org>
2022-09-21 13:17   ` J.P. [this message]
     [not found]   ` <87a66ssw7s.fsf@neverwas.me>
2022-09-21 18:35     ` Philip Kaludercic
     [not found]     ` <871qs4mv7a.fsf@posteo.net>
2022-09-22  6:23       ` J.P.
     [not found]       ` <875yhggc5s.fsf@neverwas.me>
2022-09-23 13:37         ` Philip Kaludercic
     [not found]         ` <875yheus8g.fsf@posteo.net>
2022-09-28  1:22           ` J.P.
2022-10-26 13:13 ` J.P.
2022-09-20 13:06 J.P.

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='87a66ssw7s.fsf__33782.132323698$1663769808$gmane$org@neverwas.me' \
    --to=jp@neverwas.me \
    --cc=57956@debbugs.gnu.org \
    --cc=emacs-erc@gnu.org \
    --cc=larsi@gnus.org \
    --cc=magnus.henoch@gmail.com \
    --cc=philipk@posteo.net \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).