From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: David Engster Newsgroups: gmane.emacs.devel Subject: Re: whitespace-only changes Date: Thu, 20 Aug 2020 16:54:05 +0200 Message-ID: <878se9mkqa.fsf@randomsample> References: <83imddcv4m.fsf@gnu.org> <878se9wigu.fsf@gnus.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="9862"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.91 (gnu/linux) Cc: Eli Zaretskii , rms@gnu.org, emacs-devel@gnu.org To: Lars Ingebrigtsen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Aug 20 16:55:06 2020 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1k8ly5-0002RG-WF for ged-emacs-devel@m.gmane-mx.org; Thu, 20 Aug 2020 16:55:06 +0200 Original-Received: from localhost ([::1]:33962 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1k8ly5-0005jh-2Y for ged-emacs-devel@m.gmane-mx.org; Thu, 20 Aug 2020 10:55:05 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:58758) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1k8lxH-0004y2-K8 for emacs-devel@gnu.org; Thu, 20 Aug 2020 10:54:15 -0400 Original-Received: from zplane.randomsample.de ([2a03:4000:42:1a1:9400:eeff:feb4:c8a0]:40046) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1k8lxF-0004Df-E5; Thu, 20 Aug 2020 10:54:15 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=randomsample.de; s=a; h=Content-Type:MIME-Version:Message-ID:Date: References:In-Reply-To:Subject:Cc:To:From:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=3kp28Oz/NWMi5u5tBE5HR6MZ8K++nRYBe5yZE4ySJEs=; b=dRRtctoaK3HVWuB6PqHmcRSlp iXq4/27qhSg7DNXL6tIAHBG5FgBEEaK7easPnuvW1RnOpVz7pEvFAVdmi6z2x8ukQs06P3VO43ZVa IIRuMeDZhDvY22rLzgrrRF4P2HE9uUrhhpn1eL4xjkFliafnj0CwbTgamXOvLmkSRDslnVpZGZHDm fHWMwFKlZAte+8w1ORzDVuZdVWa3gNntrYBADPLOpbrT0cpoRvw04QbL0sYa5YCb0melN0bg1gXQ8 hWOLu4aDneDfb1cJ6qbENTiAuHEx0eHkEr4BgAi+h/nx3QVMV7TXMI15hc0tnl/ZkQrflHkPdm9MZ x5CbkTarg==; Original-Received: from ip5f5abaec.dynamic.kabel-deutschland.de ([95.90.186.236] helo=void) by zplane.randomsample.de with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1k8lx9-00050h-5B; Thu, 20 Aug 2020 16:54:07 +0200 In-Reply-To: <878se9wigu.fsf@gnus.org> (Lars Ingebrigtsen's message of "Thu, 20 Aug 2020 15:32:49 +0200") Received-SPF: pass client-ip=2a03:4000:42:1a1:9400:eeff:feb4:c8a0; envelope-from=deng@randomsample.de; helo=zplane.randomsample.de X-detected-operating-system: by eggs.gnu.org: First seen = 2020/08/20 10:54:07 X-ACL-Warn: Detected OS = ??? X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:254056 Archived-At: > Eli Zaretskii writes: > >> The tool is Git, and it will treat any change as significant. I'm not >> aware of a Git option to ignore some changes based on the log >> messages. > > Me neither, but it sure would be nice to be able to tell git "this is > not a functional change" (just think of the yearly copyright notice > update). > > git has no way of verifying that it's a non-functional change, of > course, so it would just be a hint to the UI. That could then be used > by nefarious people to sneak in functional changes but mark them as > non-functional. > > So it's probably not a workable idea. I agree, but just to have mentioned it, at least 'git blame' does support ignoring commits. These can be given on the commandline or in a file (see --ignore-rev and --ignore-revs-file since version v2.23). This file could of course be generated by looking at commit messages. -David