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: CC Mode and electric-pair "problem". Date: Tue, 19 Jun 2018 05:37:21 +0300 Message-ID: <83po0nsdr2.fsf@gnu.org> References: <20180531123747.GA24752@ACM> <20180617201351.GA4580@ACM> <20180618103654.GA9771@ACM> <8336xkt967.fsf@gnu.org> <83y3fcrqjs.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 1529379300 1359 195.159.176.226 (19 Jun 2018 03:35:00 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 19 Jun 2018 03:35:00 +0000 (UTC) Cc: acm@muc.de, emacs-devel@gnu.org, tino.calancha@gmail.com, rgm@gnu.org To: =?utf-8?B?Sm/Do28gVMOhdm9yYQ==?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jun 19 05:34:55 2018 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 1fV7Pw-0000Bl-1A for ged-emacs-devel@m.gmane.org; Tue, 19 Jun 2018 05:34:52 +0200 Original-Received: from localhost ([::1]:39118 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fV7S3-0005Ed-4w for ged-emacs-devel@m.gmane.org; Mon, 18 Jun 2018 23:37:03 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:57065) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fV6WM-0008CV-Oa for emacs-devel@gnu.org; Mon, 18 Jun 2018 22:37:29 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fV6WL-0005SN-Ou for emacs-devel@gnu.org; Mon, 18 Jun 2018 22:37:26 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:55481) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fV6WH-0005RO-Ty; Mon, 18 Jun 2018 22:37:21 -0400 Original-Received: from [176.228.60.248] (port=1680 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1fV6WG-00005a-QV; Mon, 18 Jun 2018 22:37:21 -0400 In-reply-to: (message from =?utf-8?B?Sm/Do28g?= =?utf-8?B?VMOhdm9yYQ==?= on Tue, 19 Jun 2018 00:49:17 +0100) 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:226490 Archived-At: > From: João Távora > Cc: acm@muc.de, rgm@gnu.org, emacs-devel@gnu.org, tino.calancha@gmail.com > Date: Tue, 19 Jun 2018 00:49:17 +0100 > > > But putting the problematic code on a branch reduces the incentive > > even more, doesn't it? > > I don't follow. Code on a branch gets less testing by others, and therefore less reminders about the failing test. > I would answer "no", assuming the person developing the > temporarily misbehaving code is motivated to do it in the first place. > Develop and break things at will in a branch, merge them to master when > they're clean. No? If the code is used, its breakage on a branch hurts like it does on master. If it's unused, then what is it doing in the repository?