From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Paul Eggert Newsgroups: gmane.emacs.devel Subject: Re: Recommend these .gitconfig settings for git integrity. Date: Wed, 3 Feb 2016 10:10:19 -0800 Organization: UCLA Computer Science Department Message-ID: <56B2428B.10700@cs.ucla.edu> References: <87a8nlfqj9.fsf@red-bean.com> <83h9ht1o8q.fsf@gnu.org> <87mvrle8ho.fsf@red-bean.com> <56AE8126.9090708@cs.ucla.edu> <87wpqo77yc.fsf@red-bean.com> <87bn80ifmh.fsf@wanadoo.es> <87k2mo75bx.fsf@red-bean.com> <56AFB869.1080206@cs.ucla.edu> <83si1cyy3e.fsf@gnu.org> <56B06282.2050701@cs.ucla.edu> <87twlrgljm.fsf@wanadoo.es> <56B0ED78.5030209@cs.ucla.edu> <878u33gd99.fsf@wanadoo.es> <56B1ACB4.7090705@cs.ucla.edu> <87k2ml4vfk.fsf@wanadoo.es> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1454523076 14045 80.91.229.3 (3 Feb 2016 18:11:16 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 3 Feb 2016 18:11:16 +0000 (UTC) To: =?UTF-8?Q?=c3=93scar_Fuentes?= , emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Feb 03 19:11:11 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1aR1tV-0001Uk-MK for ged-emacs-devel@m.gmane.org; Wed, 03 Feb 2016 19:11:09 +0100 Original-Received: from localhost ([::1]:36836 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aR1tU-0006SP-Nh for ged-emacs-devel@m.gmane.org; Wed, 03 Feb 2016 13:11:08 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:51745) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aR1sp-0006Jd-D4 for emacs-devel@gnu.org; Wed, 03 Feb 2016 13:10:33 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aR1sk-0006Dn-Ar for emacs-devel@gnu.org; Wed, 03 Feb 2016 13:10:27 -0500 Original-Received: from zimbra.cs.ucla.edu ([131.179.128.68]:52418) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aR1sk-0006Dc-3l for emacs-devel@gnu.org; Wed, 03 Feb 2016 13:10:22 -0500 Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id E490E160D70; Wed, 3 Feb 2016 10:10:20 -0800 (PST) Original-Received: from zimbra.cs.ucla.edu ([127.0.0.1]) by localhost (zimbra.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id TjJrtqy4iLUe; Wed, 3 Feb 2016 10:10:20 -0800 (PST) Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id 32379160E5D; Wed, 3 Feb 2016 10:10:20 -0800 (PST) X-Virus-Scanned: amavisd-new at zimbra.cs.ucla.edu Original-Received: from zimbra.cs.ucla.edu ([127.0.0.1]) by localhost (zimbra.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 5FfL0glwtoj1; Wed, 3 Feb 2016 10:10:20 -0800 (PST) Original-Received: from penguin.cs.ucla.edu (Penguin.CS.UCLA.EDU [131.179.64.200]) by zimbra.cs.ucla.edu (Postfix) with ESMTPSA id 192B7160D70; Wed, 3 Feb 2016 10:10:20 -0800 (PST) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 In-Reply-To: <87k2ml4vfk.fsf@wanadoo.es> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 131.179.128.68 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 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-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:199258 Archived-At: On 02/03/2016 08:20 AM, =C3=93scar Fuentes wrote: > Instead of making up reasons and proving yourself right, the > reasonable thing to do is to ask the git maintainers. I'd rather not waste their time on this unless the concerns are=20 warranted. We would ill-serve Emacs development by giving ourselves a=20 reputation for cluelessness. Let's wait for real problems to turn up=20 before ringing alarm bells elsewhere. > It either works or doesn't. It does both, and we're concerned about the part that doesn't work. A=20 client can operate for a while with tainted objects, and do (say) a=20 rebase that computes new checksums for the bad data, and then ship the=20 tainted data off to the server with the newly computed checksums. The=20 server can't detect the problem because the recomputed checksums match=20 the tainted data. > in the future, I would appreciate if you discuss a change like this=20 > before rushing to commit it and cause irreversible consequences.=20 The consequences are largely benign and entirely reversible. I often install changes to Emacs, and obviously can't clear each change=20 before installing it, as that would slow us all down for little benefit.=20 So I use my best judgment to decide which changes to install in master,=20 which in emacs-25, and which to discuss first. I sometimes make mistakes=20 in that area, for which I apologize, but what can I say? The only way to=20 prevent all mistaken changes is to not make any changes. This change=20 seemed like a no-brainer at the time, but we've decided to take a more=20 cautious approach for now. Such things happen, and life moves on.