From: Ted Zlatanov <tzz@lifelogs.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: open-{gnutls,network}-stream backwards compatibility
Date: Wed, 02 Jan 2019 20:25:30 +0000 [thread overview]
Message-ID: <a7kig62t.fsf@lifelogs.com> (raw)
In-Reply-To: <83wonm3km6.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 02 Jan 2019 21:49:53 +0200")
On Wed, 02 Jan 2019 21:49:53 +0200 Eli Zaretskii <eliz@gnu.org> wrote:
EZ> I appreciate your authorship, but in Emacs, once we release our code,
EZ> we no longer have much of control on it. It's out in the open.
I wasn't claiming ownership, but rather pointing out what in retrospect
is not a good design because it hides useful options that need to be
passed through. This is, regardless of the owner, bad code.
The author IMO has a responsibility to recognize this situation.
EZ> Deprecation is a nuisance: it chatters when you compile code, it nags.
EZ> We need a seriously good reason to impose that on unsuspecting users.
There's only one user, is what I'm saying... `open-gnutls-stream' is
just not that popular, fortunately. So we can just kill it and the end
users won't notice.
I'm OK with Robert's suggestion to leave it in place but unused as well.
It's just that it seems like avoiding deprecation in name only.
Ted
next prev parent reply other threads:[~2019-01-02 20:25 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
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 [this message]
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=a7kig62t.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@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.
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.