From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: =?utf-8?B?Sm/Do28gVMOhdm9yYQ==?= Newsgroups: gmane.emacs.devel Subject: Re: CC Mode and electric-pair "problem". Date: Tue, 19 Jun 2018 09:13:10 +0100 Message-ID: References: <20180531123747.GA24752@ACM> <20180617201351.GA4580@ACM> <20180618103654.GA9771@ACM> <8336xkt967.fsf@gnu.org> <83y3fcrqjs.fsf@gnu.org> <83po0nsdr2.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: blaine.gmane.org 1529395928 24636 195.159.176.226 (19 Jun 2018 08:12:08 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 19 Jun 2018 08:12:08 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (darwin) Cc: acm@muc.de, emacs-devel@gnu.org, tino.calancha@gmail.com, rgm@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jun 19 10:12:03 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 1fVBk9-0006FO-Ft for ged-emacs-devel@m.gmane.org; Tue, 19 Jun 2018 10:12:01 +0200 Original-Received: from localhost ([::1]:39940 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fVBmG-0004KI-FT for ged-emacs-devel@m.gmane.org; Tue, 19 Jun 2018 04:14:12 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:52637) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fVBlR-0004Iy-RF for emacs-devel@gnu.org; Tue, 19 Jun 2018 04:13:22 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fVBlN-0004Mr-SE for emacs-devel@gnu.org; Tue, 19 Jun 2018 04:13:21 -0400 Original-Received: from mail-wr0-x22a.google.com ([2a00:1450:400c:c0c::22a]:45628) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fVBlN-0004Li-LB; Tue, 19 Jun 2018 04:13:17 -0400 Original-Received: by mail-wr0-x22a.google.com with SMTP id o12-v6so19498414wrm.12; Tue, 19 Jun 2018 01:13:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version:content-transfer-encoding; bh=45DhuM0UzHcdVa16We/ZL3MggMUyreAEYSH0rk9uL3g=; b=IhwjLgcB/LKQ1lirL6/mKAkS7LJV8bYoaq6npXmhJrHm0Tw1i87RdgwZGyWpKJ/qfU aPgWh3HsV5kdsTwNNKfjQ3CJx6cDo1/ANApzSl/dkDw4sBrRDl9KujPkeuTemUwmdq4o KsJTOWzRlcOFb6dU1jJgzLXJsyhcH4nrIftJqOHmOIDaM2fl7fMGJuySPRuUh/Q8xorg 27YaslJkKYBVc2c+i3wN7zWIP7St90cWAcYxqcGiz/u7OS5GbFx+Dtn7TG6UOSBUaAOt l6bQhsTE+Akk93XUzjNeWiMqkH+6jhjwlZxzp/c5yLJEofAVJ3Y3ojMhs0saOaeEqSVA g1og== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:references:date:in-reply-to :message-id:user-agent:mime-version:content-transfer-encoding; bh=45DhuM0UzHcdVa16We/ZL3MggMUyreAEYSH0rk9uL3g=; b=uNfnxCnHiS0ujDSPU6/ALlhtqVH6nDo0BNGGBPhnFmvsfYnrO32gygrNh9Pm/RGjG0 ZzhflJzRqyPJSLzQxpezcTIvIBZrq+fEjXbB+od/Lg+ZEittSQKqEV2YcMJHQTBTZH0g DrN0/lsrFL1jik7rujaU8Rz2Hs5d/o8cmniXDM+cTiOMW9k3JsVUT72yiPO/AfPkv1lT 5aG6r5aRP6Pk/SZcRJWG0JM4gkNAKfp6JP9yMq07tcLfN58KOzCLorVgo2UnljtXynrW z10n++wXyrTO/dwXkcipBzeeIjKERazTx+ELPuOXULuDxhsGNgPSi5VXQCVx0cz26WlX ScTQ== X-Gm-Message-State: APt69E0ft0/w4f4M/+Gr8smF520p36wNQtp5SMtyITvf8wbjvp9xBPYB kuLmF400SPfH7swUl/pRHnc= X-Google-Smtp-Source: ADUXVKKMs/8hQOdZNWSaZoXcEIEEOHICmr/zP1ajyfXSGqOhJ5jac8i0FeAi5cdFe0mLbdaF/hZ3Uw== X-Received: by 2002:adf:f40a:: with SMTP id g10-v6mr12962169wro.256.1529395996618; Tue, 19 Jun 2018 01:13:16 -0700 (PDT) Original-Received: from kitaj.yourcompany.com (178.110.103.87.rev.vodafone.pt. [87.103.110.178]) by smtp.gmail.com with ESMTPSA id h7-v6sm8577241wmc.44.2018.06.19.01.13.14 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 19 Jun 2018 01:13:15 -0700 (PDT) In-Reply-To: <83po0nsdr2.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 19 Jun 2018 05:37:21 +0300") X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2a00:1450:400c:c0c::22a 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:226495 Archived-At: Eli Zaretskii writes: >> From: Jo=C3=A3o T=C3=A1vora >> Cc: acm@muc.de, rgm@gnu.org, emacs-devel@gnu.org, tino.calancha@gmail= .com >> Date: Tue, 19 Jun 2018 00:49:17 +0100 >>=20 >> > But putting the problematic code on a branch reduces the incentive >> > even more, doesn't it? >>=20 >> I don't follow. > > Code on a branch gets less testing by others, and therefore less > reminders about the failing test. But surely, the programmer who broke the test, who is the person technically (and morally) most well suited to fix the problem has the all the original incentive to merge his work. For me this is very clear: only merge if there are 0 failing tests (or rather, if you've increased the number of failing tests by 0). Perhaps CVS used to make this impractival, but nowadays git branches make this very easy. BTW, why does CONTRIBUTE tell us to "make check" at all? >> 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. Not at all, no, it hurts only the people interested in trying out the feature. On master it hurts everyone, including Hydra's continuous integration, for example, which is the issue at hand. But also other automated things like automated bug bisections etc... > If it's unused, then what is it doing in the repository? To save it. To show it to others for comments. This seems rather obvious to me, so perhaps we are misunderstanding each other. I'm also pretty sure I've seen branches prescribed in this list for unstable features.