From: Dmitry Gutov <dgutov@yandex.ru>
To: John Wiegley <jwiegley@gmail.com>, Eli Zaretskii <eliz@gnu.org>
Cc: 23750@debbugs.gnu.org, sdl.web@gmail.com, monnier@IRO.UMontreal.CA
Subject: bug#23750: 25.0.95; bug in url-retrieve or json.el
Date: Sun, 19 Jun 2016 21:45:24 +0300 [thread overview]
Message-ID: <8f51ca52-d0fd-6647-cfa8-82434a3057b5@yandex.ru> (raw)
In-Reply-To: <m2d1nddoad.fsf@newartisans.com>
On 06/19/2016 09:30 PM, John Wiegley wrote:
> Bear in mind that 25.2 can be released as soon after as we want it to. If
> anything is "optional" at this point in time, it should be deferred.
Let's apply the few outstanding patches and release 25.2 the next day, then?
Traditionally, releases are separated by at least several months, even
ones with no big changes.
> We shouldn't try to race anything into the release, just because we think
> users will then have to live with some minor inferior behavior for a long time
> after. The description above certainly does not sound like something that
> needs to be happen for 25.1.
Just to be clear: the patch doesn't change the behavior of any working
code. It just catches a particular kind of bug earlier than it would
manifest through a cryptic behavior.
Behavior which is non-trivial to debug, and thus adds to the already
non-trivial effort required of a person writing an advanced language
support code (using an external daemon talking over HTTP is fairly
common for this these days).
next prev parent reply other threads:[~2016-06-19 18:45 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-12 2:22 bug#23750: 25.0.95; bug in url-retrieve or json.el Leo Liu
2016-06-13 15:02 ` Dmitry Gutov
2016-06-13 17:55 ` Stefan Monnier
2016-06-13 19:26 ` Dmitry Gutov
2016-06-14 0:30 ` Stefan Monnier
2016-06-19 18:14 ` Dmitry Gutov
2016-06-19 18:25 ` Eli Zaretskii
2016-06-19 18:30 ` John Wiegley
2016-06-19 18:45 ` Dmitry Gutov [this message]
2016-06-19 19:56 ` John Wiegley
2016-06-19 20:05 ` Dmitry Gutov
2016-06-19 21:07 ` John Wiegley
2016-06-20 1:28 ` Glenn Morris
2016-06-20 4:22 ` John Wiegley
2016-06-20 12:39 ` Lars Ingebrigtsen
2016-07-01 20:49 ` John Wiegley
2016-06-20 14:42 ` Eli Zaretskii
2016-06-23 17:14 ` Glenn Morris
2016-06-20 1:26 ` Glenn Morris
2016-06-20 2:58 ` Dmitry Gutov
2016-06-19 18:36 ` Dmitry Gutov
2016-06-20 0:15 ` Leo Liu
2016-06-20 14:39 ` Eli Zaretskii
2016-06-20 2:40 ` Eli Zaretskii
2016-06-20 2:51 ` Dmitry Gutov
2016-06-20 14:38 ` Eli Zaretskii
2016-06-20 14:54 ` Dmitry Gutov
2016-06-20 15:03 ` Eli Zaretskii
2016-06-20 17:16 ` Dmitry Gutov
2016-06-20 20:17 ` Eli Zaretskii
2016-06-20 20:27 ` Dmitry Gutov
2016-06-21 2:30 ` Eli Zaretskii
2016-06-21 13:51 ` Dmitry Gutov
2016-06-21 15:18 ` Eli Zaretskii
2016-06-22 1:08 ` John Wiegley
2016-06-22 2:36 ` Eli Zaretskii
2016-06-22 18:21 ` Dmitry Gutov
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=8f51ca52-d0fd-6647-cfa8-82434a3057b5@yandex.ru \
--to=dgutov@yandex.ru \
--cc=23750@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jwiegley@gmail.com \
--cc=monnier@IRO.UMontreal.CA \
--cc=sdl.web@gmail.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 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).