From: Eli Zaretskii <eliz@gnu.org>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: emacs-devel@gnu.org
Subject: Re: open-{gnutls,network}-stream backwards compatibility
Date: Wed, 02 Jan 2019 20:30:22 +0200 [thread overview]
Message-ID: <83y3823oap.fsf@gnu.org> (raw)
In-Reply-To: <k1jnexo9.fsf@lifelogs.com> (message from Ted Zlatanov on Wed, 02 Jan 2019 18:12:22 +0000)
> From: Ted Zlatanov <tzz@lifelogs.com>
> Date: Wed, 02 Jan 2019 18:12:22 +0000
>
> On Wed, 02 Jan 2019 18:47:55 +0100 Robert Pluim <rpluim@gmail.com> wrote:
>
> RP> So nil/t would mean :nowait nil/t, and anything else would be a
> RP> plist. Itʼs not perfect, but I guess backwards compatibility is
> RP> important.
>
> I like that approach as well, noting also that the `open-gnutls-stream' docs say
>
> This is a very simple wrapper around `gnutls-negotiate'
>
> which in turn takes a plist. So maybe the callers should just call
> `gnutls-negotiate', and `open-gnutls-stream' should be deprecated
> because it has failed to be a simple wrapper :)
If we can make the change backward-compatible, there's no reason to
deprecate it.
next prev parent reply other threads:[~2019-01-02 18:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-02 16:49 open-{gnutls,network}-stream backwards compatibility Robert Pluim
2019-01-02 17:04 ` Eli Zaretskii
2019-01-02 17:47 ` Robert Pluim
2019-01-02 18:07 ` Eli Zaretskii
2019-01-02 18:56 ` Robert Pluim
2019-01-04 14:06 ` Eli Zaretskii
2019-01-04 22:29 ` Robert Pluim
2019-01-05 6:58 ` Eli Zaretskii
2019-01-05 7:36 ` Robert Pluim
2019-01-05 8:40 ` Eli Zaretskii
2019-01-09 21:50 ` Robert Pluim
2019-01-10 15:53 ` Ted Zlatanov
2019-01-10 16:05 ` Eli Zaretskii
2019-01-12 11:16 ` Eli Zaretskii
2019-01-02 18:12 ` Ted Zlatanov
2019-01-02 18:30 ` Eli Zaretskii [this message]
2019-01-02 19:18 ` Ted Zlatanov
2019-01-02 19:49 ` Eli Zaretskii
2019-01-02 20:01 ` Robert Pluim
2019-01-02 20:25 ` Ted Zlatanov
2019-01-04 11:15 ` Robert Pluim
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=83y3823oap.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=tzz@lifelogs.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.