From: Eli Zaretskii <eliz@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: dgutov@yandex.ru, jtamagnan@gmail.com, 23609@debbugs.gnu.org
Subject: bug#23609: 25.0.92; Python eldoc freeze
Date: Fri, 27 May 2016 21:41:35 +0300 [thread overview]
Message-ID: <83shx3z6lc.fsf@gnu.org> (raw)
In-Reply-To: <174m9jzew1.fsf@fencepost.gnu.org> (message from Glenn Morris on Fri, 27 May 2016 11:42:22 -0400)
> From: Glenn Morris <rgm@gnu.org>
> Cc: jtamagnan@gmail.com, dgutov@yandex.ru, 23609@debbugs.gnu.org
> Date: Fri, 27 May 2016 11:42:22 -0400
>
> Eli Zaretskii wrote:
>
> > Please don't add this bug to the list of those which block 25.1
> > without discussing that here first.
>
> That's a new rule.
No, it isn't. I was asked whether the bug should block, and answered
that it shouldn't, providing my rationale. Given that answer, common
sense would have it that adding the bug to the list without discussion
is not TRT.
> It's a bad regression that could easily be worked around by defaulting
> eldoc mode to off in python mode. That could be done very easily.
That a bug doesn't block the release doesn't mean it cannot be easily
fixed, or that a fix won't be accepted on the release branch. I said
that as well back when I was asked.
next prev parent reply other threads:[~2016-05-27 18:41 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-24 15:34 bug#23609: 25.0.92; Python eldoc freeze Jules Tamagnan
2016-05-25 6:11 ` Andreas Röhler
2016-05-25 15:18 ` Jules Tamagnan
2016-05-25 15:33 ` Andreas Röhler
2016-05-26 15:52 ` Jules Tamagnan
2016-05-26 16:31 ` Eli Zaretskii
2016-05-26 16:37 ` Dmitry Gutov
2016-05-26 16:48 ` Eli Zaretskii
2016-05-26 17:13 ` Jules Tamagnan
2016-05-27 9:23 ` Eli Zaretskii
2016-05-27 14:41 ` Eli Zaretskii
2016-05-27 14:52 ` Jules Tamagnan
2016-05-27 19:06 ` Eli Zaretskii
2016-05-27 15:42 ` Glenn Morris
2016-05-27 18:41 ` Eli Zaretskii [this message]
2016-05-27 16:12 ` Jules Tamagnan
2016-05-27 16:18 ` Dmitry Gutov
2016-05-27 17:12 ` Jules Tamagnan
2016-05-27 18:26 ` Dmitry Gutov
2016-05-27 18:39 ` Jules Tamagnan
2016-05-27 18:50 ` Dmitry Gutov
2016-05-27 18:57 ` Jules Tamagnan
2016-05-27 19:05 ` Eli Zaretskii
2016-05-27 19:13 ` Jules Tamagnan
2016-05-27 19:30 ` Eli Zaretskii
2016-05-27 19:43 ` Jules Tamagnan
2016-05-27 19:49 ` Eli Zaretskii
2016-05-27 20:19 ` Jules Tamagnan
2016-05-28 7:53 ` Eli Zaretskii
2016-05-31 17:35 ` Jules Tamagnan
2016-06-06 14:08 ` Jules Tamagnan
2016-06-06 15:15 ` Eli Zaretskii
2016-06-10 9:10 ` Eli Zaretskii
2016-05-27 6:09 ` Andreas Röhler
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=83shx3z6lc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=23609@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=jtamagnan@gmail.com \
--cc=rgm@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.