From: Eli Zaretskii <eliz@gnu.org>
To: Philipp Stephani <phst@google.com>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] emacs-25 d4e1549: Guard terminal parameter in XTerm mouse mode
Date: Thu, 24 Nov 2016 18:23:57 +0200 [thread overview]
Message-ID: <83fumg6e3m.fsf@gnu.org> (raw)
In-Reply-To: <CAP-RRPuzZic-msgJqJKjHNY13V48o3zs2SARW6YJCBZJ8Q=aEA@mail.gmail.com> (message from Philipp Stephani on Thu, 24 Nov 2016 08:58:28 +0000)
> From: Philipp Stephani <phst@google.com>
> Date: Thu, 24 Nov 2016 08:58:28 +0000
> Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
>
> > It's a very annoying and highly visible bug, and the fix is trivial and cannot possibly break anything.
>
> It wasn't reported until now, was it? So I guess it's only visible
> under some conditions that don't happen very often.
>
> It happens always when selecting text with the mouse in HTerm, I think that happens very often. Perhaps
> people just ignore the error message most of the time.
Perhaps. But that probably means it isn't urgent to fix, especially
if we had this with us for quite some time.
> Can you tell since when do we have this bug? If it exists long
> enough, I don't think we should do this on the release branch, it goes
> against the criteria for bug fixes there.
>
> What are the criteria?
As described here:
http://lists.gnu.org/archive/html/emacs-devel/2016-10/msg00007.html
http://lists.gnu.org/archive/html/emacs-devel/2016-10/msg00460.html
http://lists.gnu.org/archive/html/bug-gnu-emacs/2016-10/msg00787.html
> CONTRIBUTE states
> "Release branches […] are mainly
> intended for more-conservative changes such as bug fixes. […]
> If you are fixing a bug that exists in the current release, be sure to
> commit it to the release branch; […]"
That's a general policy, but Emacs 25.2 has special rules because we
want to put it out the door very soon.
> If the actual policy is different, please document it in CONTRIBUTE.
I don't think it's right to publish ad-hoc criteria in CONTRIBUTE,
that would be confusing to new contributors.
> I've seen some talk about bugfix-only releases, but I think the policy should be clearer and better documented
> to avoid such discussions.
I don't see any good alternative to reading the mailing lists, sorry.
prev parent reply other threads:[~2016-11-24 16:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20161122204222.29398.86534@vcs.savannah.gnu.org>
[not found] ` <20161122204222.DBE712201C5@vcs.savannah.gnu.org>
2016-11-23 1:08 ` [Emacs-diffs] emacs-25 d4e1549: Guard terminal parameter in XTerm mouse mode Stefan Monnier
2016-11-23 12:20 ` Philipp Stephani
2016-11-23 15:54 ` Eli Zaretskii
2016-11-23 17:09 ` Philipp Stephani
2016-11-23 17:22 ` Eli Zaretskii
2016-11-24 8:58 ` Philipp Stephani
2016-11-24 16:23 ` Eli Zaretskii [this message]
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=83fumg6e3m.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=phst@google.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.