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: git history tracking across renames (and emacs support) Date: Tue, 10 Jul 2018 18:36:23 +0300 Message-ID: <838t6jgl1k.fsf@gnu.org> References: <87a7yn7tqp.fsf@lifelogs.com> <878te75xa1.fsf@lifelogs.com> <87ind6l2tt.fsf@lifelogs.com> <877etklvsa.fsf@lifelogs.com> <83y3m0pv8u.fsf@gnu.org> <86608msw0h.fsf@dod.no> <838tdiet25.fsf@gnu.org> <87y3li4vh7.fsf@telefonica.net> <87efnan46u.fsf@linux-m68k.org> <86wp12qtgo.fsf@dod.no> <83tvw6chqv.fsf@gnu.org> <86shbprix7.fsf_-_@dod.no> NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1531238049 10641 195.159.176.226 (10 Jul 2018 15:54:09 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 10 Jul 2018 15:54:09 +0000 (UTC) Cc: larsi@gnus.org, emacs-devel@gnu.org To: Ted Zlatanov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jul 10 17:54:04 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 1fcuxl-0002aV-20 for ged-emacs-devel@m.gmane.org; Tue, 10 Jul 2018 17:54:01 +0200 Original-Received: from localhost ([::1]:48518 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fcuzr-0006Cl-U2 for ged-emacs-devel@m.gmane.org; Tue, 10 Jul 2018 11:56:12 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:42293) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fcugc-0007jn-Cb for emacs-devel@gnu.org; Tue, 10 Jul 2018 11:36:21 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fcugX-0006il-Rx for emacs-devel@gnu.org; Tue, 10 Jul 2018 11:36:18 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:60984) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fcugX-0006id-NT; Tue, 10 Jul 2018 11:36:13 -0400 Original-Received: from [176.228.60.248] (port=3427 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1fcugX-0001n8-3G; Tue, 10 Jul 2018 11:36:13 -0400 In-reply-to: (message from Ted Zlatanov on Tue, 10 Jul 2018 13:14:39 +0000) 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:227213 Archived-At: > From: Ted Zlatanov > Date: Tue, 10 Jul 2018 13:14:39 +0000 > Cc: emacs-devel@gnu.org > > On Tue, 02 Jan 2018 09:49:41 +0100 Lars Ingebrigtsen wrote: > > LI> Paul Eggert writes: > >> What would be most helpful (and I realize I'm asking for a lot) would > >> be ChangeLog entries or commit messages (it doesn't matter which) that > >> explain the *motivation* for each change. In contrast, often it is > >> counterproductive to burden commit messages with mechanical details > >> such as naming each and every function that was modified, as it wastes > >> developers' time to wade through these details when they're trying to > >> look for stuff that's more important. > > LI> Hear, hear. > > I would appreciate that too. If I need to know what functions were > modified, I look at the diff, which Git makes trivial. > > Is there any chance of evolving the commit message formatting > requirements to lower the friction of making a commit and reduce > redundancy? IMO, what you'd like to have will actually _raise_ the friction (i.e. will be harder to provide) for many contributors, according to my experience of reviewing quite a few patches.