From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: [Emacs-diffs] emacs-25 d4e1549: Guard terminal parameter in XTerm mode Date: Mon, 28 Nov 2016 17:51:34 +0200 Message-ID: <83k2bnzjp5.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: blaine.gmane.org 1480348344 27062 195.159.176.226 (28 Nov 2016 15:52:24 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 28 Nov 2016 15:52:24 +0000 (UTC) Cc: emacs-devel@gnu.org To: Philipp Stephani Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Nov 28 16:52:20 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cBOE2-0005iX-P3 for ged-emacs-devel@m.gmane.org; Mon, 28 Nov 2016 16:52:14 +0100 Original-Received: from localhost ([::1]:59579 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cBOE6-0000K8-H9 for ged-emacs-devel@m.gmane.org; Mon, 28 Nov 2016 10:52:18 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:44889) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cBODR-0000K1-Pp for emacs-devel@gnu.org; Mon, 28 Nov 2016 10:51:38 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cBODO-0007WY-Nj for emacs-devel@gnu.org; Mon, 28 Nov 2016 10:51:37 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:43781) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cBODO-0007WS-K0; Mon, 28 Nov 2016 10:51:34 -0500 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:2899 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1cBODO-0007NI-0B; Mon, 28 Nov 2016 10:51:34 -0500 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:209649 Archived-At: Ping! I still think this patch should be moved to master. > > > 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.