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), Re: git history tracking across renames (and emacs support), Re: git history tracking across renames (and emacs support), Re: git history tracking across renames (and emacs support) Date: Wed, 11 Jul 2018 18:42:02 +0300 Message-ID: <83in5lg4ol.fsf@gnu.org> References: <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> <83o9fefnv9.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1531323670 30529 195.159.176.226 (11 Jul 2018 15:41:10 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 11 Jul 2018 15:41:10 +0000 (UTC) Cc: larsi@gnus.org, monnier@iro.umontreal.ca, emacs-devel@gnu.org To: Ted Zlatanov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jul 11 17:41:05 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 1fdHEn-0007pV-GQ for ged-emacs-devel@m.gmane.org; Wed, 11 Jul 2018 17:41:05 +0200 Original-Received: from localhost ([::1]:54394 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fdHGu-0006Si-KJ for ged-emacs-devel@m.gmane.org; Wed, 11 Jul 2018 11:43:16 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:59564) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fdHG0-0006PM-W0 for emacs-devel@gnu.org; Wed, 11 Jul 2018 11:42:24 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fdHFw-0000H2-Gj for emacs-devel@gnu.org; Wed, 11 Jul 2018 11:42:21 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:52702) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fdHFl-00006m-B3; Wed, 11 Jul 2018 11:42:05 -0400 Original-Received: from [176.228.60.248] (port=2038 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1fdHFk-0005AF-Ql; Wed, 11 Jul 2018 11:42:05 -0400 In-reply-to: (message from Ted Zlatanov on Wed, 11 Jul 2018 13:54:49 +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:227250 Archived-At: > From: Ted Zlatanov > Cc: Marcin Borkowski , Stefan Monnier , emacs-devel@gnu.org, larsi@gnus.org > Date: Wed, 11 Jul 2018 13:54:49 +0000 > > Emacs does not produce the format mechanically, unless you know the > right commands. It's IMHO a pain to learn them. There's only one command: "C-x 4 a". > EZ> It summarizes diffs, in a way, yes (and allows to add explanations if > EZ> appropriate). I don't see that as a disadvantage: you don't always > EZ> have the ability to generate diffs (e.g., in a release tarball). > > Releases communicate through NEWS and release notes. > > If the users need to read the commit logs to find what files and > functions have changed since the last release, something's wrong with > the release process. We have no release notes except NEWS. And NEWS only mentions new features and changes in behavior, it doesn't mention bugfixes, which is a large portion (if not the majority) of changes in any release. ChangeLog files provide information about changes when one has no up-to-date repository around. > As Stefan said, it's mainly because I don't do it as often as you. > Familiarity takes time to achieve and sustain. In this case, it feels > like I'm doing work to satisfy the computer rather than to improve Emacs. This old curmudgeon found solution to such situations: where I do something rarely enough to be unable to trust my memory, I keep notes. It's a surprisingly effective and efficient way, you should try that some time. > I'm advocating readability and less mechanical content, not conciseness > for its own sake. I understand. I'm just saying that it takes more time and effort to generate such less mechanical content, so you are probably raising the bar, not lowering it. > Log messages don't have to be carved in stone. You're justifying a human > cost with a technical side effect of the version control system. It doesn't have to be so, but AFAIK the last VCS where log messages could be amended was CVS. In our brave new world, log messages _are_ carved in stone once committed. That's the reality in which we live, whether we like it or not. > I agree it's hard to explain what should be in a log message, but that's > because there's no perfect solution to the problem of writing down the > thought process and decisions that led to a solution. Certainly, I don't > think the current mechanical content improves that situation. It > *formalizes* the description of a specific subset of the decisions. It gives me easy tools to teach newcomers how to write log messages we want to see. Once this is taken from me, what can I say to a contributor who claims that his/her log message is just fine, because there's nothing in CONTRIBUTE to say it isn't? > Maybe there's a format that can link better and with less effort between > code and commit description in these complex cases. If someone would like to write a command that looks at the last commit (or several commits), and generates a skeleton of a log entry, I'm all for it. (People will have to "git commit --amend" to use such a command, but that's not a problem, I think, and could also be automated.)