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: Sat, 13 Jan 2018 10:31:39 +0200 Message-ID: <83po6e17o4.fsf@gnu.org> References: <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> <7c7503b4-1f82-8a25-fedd-c61c3e7629f6@cs.ucla.edu> <83zi5o6w4p.fsf@gnu.org> <745d2f02-8ca3-8962-0de4-053340c8fa63@cs.ucla.edu> <83efmx6862.fsf@gnu.org> <83wp0n32se.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1515832283 19343 195.159.176.226 (13 Jan 2018 08:31:23 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 13 Jan 2018 08:31:23 +0000 (UTC) Cc: emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jan 13 09:31:19 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 1eaHDe-0004Md-5z for ged-emacs-devel@m.gmane.org; Sat, 13 Jan 2018 09:31:14 +0100 Original-Received: from localhost ([::1]:49677 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eaHFd-0005kL-UT for ged-emacs-devel@m.gmane.org; Sat, 13 Jan 2018 03:33:17 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:58755) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eaHER-0005jK-OZ for emacs-devel@gnu.org; Sat, 13 Jan 2018 03:32:06 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eaHEM-0002BE-Rk for emacs-devel@gnu.org; Sat, 13 Jan 2018 03:32:03 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:42704) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eaHEM-0002B5-OI; Sat, 13 Jan 2018 03:31:58 -0500 Original-Received: from [176.228.60.248] (port=4796 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1eaHEM-0004ag-4g; Sat, 13 Jan 2018 03:31:58 -0500 In-reply-to: (message from Stefan Monnier on Sat, 13 Jan 2018 00:13:13 -0500) 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:221915 Archived-At: > From: Stefan Monnier > Date: Sat, 13 Jan 2018 00:13:13 -0500 > > I'm not particularly concerned about "easing the burden", but rather > about improving the quality: when the commit message just paraphrases > the diff, the commit message is not very useful Since ChangeLog is generated from Git log, it _is_ useful when all you have is the ChangeLog. Which could happen if, for example, you want to work on Emacs while off-line during a long flight. > and would benefit from being rephrased so as to give more > information about the intention/motivation behind the change > (information not readily available from the diff). I already suggested near the beginning of this bike-shedding the way of making the reasons more visible. What we need is to have more people, including the veteran contributors, write better commentary for their changes, and then we'll be just fine. Commit log messages are not the best place for this information, and should be used only as the last resort.