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: Fri, 13 Jul 2018 17:39:51 +0300 Message-ID: <83k1pzci88.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> <838t6jgl1k.fsf@gnu.org> <601m6cc6.fsf@lifelogs.com> <83o9fefnv9.fsf@gnu.org> <83d0vtfx4f.fsf@gnu.org> <83o9fce4np.fsf@gnu.org> <8336wneemw.fsf@gnu.org> <907edf27-ed0c-5166-88ea-c3db9d9d7f74@cs.ucla.edu> NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1531492721 7428 195.159.176.226 (13 Jul 2018 14:38:41 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 13 Jul 2018 14:38:41 +0000 (UTC) Cc: tzz@lifelogs.com, radon.neon@gmail.com, larsi@gnus.org, emacs-devel@gnu.org To: Paul Eggert Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jul 13 16:38:36 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 1fdzDQ-0001ng-Oh for ged-emacs-devel@m.gmane.org; Fri, 13 Jul 2018 16:38:36 +0200 Original-Received: from localhost ([::1]:37678 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fdzFW-0005kg-6O for ged-emacs-devel@m.gmane.org; Fri, 13 Jul 2018 10:40:46 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:35996) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fdzEn-0005ju-5A for emacs-devel@gnu.org; Fri, 13 Jul 2018 10:40:04 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fdzEi-0004b2-75 for emacs-devel@gnu.org; Fri, 13 Jul 2018 10:40:01 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:47950) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fdzEi-0004Zz-23; Fri, 13 Jul 2018 10:39:56 -0400 Original-Received: from [176.228.60.248] (port=1243 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1fdzEf-0004wx-QJ; Fri, 13 Jul 2018 10:39:55 -0400 In-reply-to: <907edf27-ed0c-5166-88ea-c3db9d9d7f74@cs.ucla.edu> (message from Paul Eggert on Fri, 13 Jul 2018 09:15:55 -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:227340 Archived-At: > Cc: tzz@lifelogs.com, larsi@gnus.org, emacs-devel@gnu.org > From: Paul Eggert > Date: Fri, 13 Jul 2018 09:15:55 -0500 > > On 07/13/2018 03:14 AM, Eli Zaretskii wrote: > > I find the summary line to be a nuisance in too many cases. > > Although the summary line is sometimes a nuisance to write, when done > well it is so useful that it's clearly a net win over our old way of > doing things. Many Git user interfaces list only the summary lines, and > for good reason: they let you quickly scan a list of commits looking for > what happened in those commits. Writing a useful summary line is thus a > real service to later developers, and is far more helpful than the file, > function and variable names that the GNU coding standards currently > require in ChangeLogs. > > The primary UI that we promote on the web > lists just summary lines. I > just now looked at the most recent ten summary lines in Emacs master, > and eight of them seemed useful. The two I found less useful were > "Unbreak bootstrap" (a motivation for the change, but not enough > description) and "Fix Bug#32107" (likewise). It'd be helpful for us to > encourage people to write commit messages with summary lines that are > suitable for later readers. All true. Like I said: this is the price we pay for using Git and related UIs instead of ChangeLog, where header lines were optional, to be used where that really made sense (which was relatively rare). With Git, they're mandatory, because if we don't use them, various dependent features will not work well, or not at all. Like almost every other feature, this one has its price.