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: Wed, 03 Jan 2018 17:36:31 +0200 Message-ID: <83po6rar9c.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> <83608kck4c.fsf@gnu.org> <544c170f-99bd-c701-3063-c697296a30a6@cs.ucla.edu> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1514993687 23954 195.159.176.226 (3 Jan 2018 15:34:47 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 3 Jan 2018 15:34:47 +0000 (UTC) Cc: emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jan 03 16:34:43 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 1eWl3w-0005aG-HR for ged-emacs-devel@m.gmane.org; Wed, 03 Jan 2018 16:34:40 +0100 Original-Received: from localhost ([::1]:55832 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eWl5t-0003Y7-TD for ged-emacs-devel@m.gmane.org; Wed, 03 Jan 2018 10:36:41 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:43572) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eWl5n-0003Xl-Sx for emacs-devel@gnu.org; Wed, 03 Jan 2018 10:36:36 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eWl5k-0000c0-0c for emacs-devel@gnu.org; Wed, 03 Jan 2018 10:36:35 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:60466) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eWl5j-0000bu-T8; Wed, 03 Jan 2018 10:36:31 -0500 Original-Received: from [176.228.60.248] (port=2163 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1eWl5j-0000ev-B7; Wed, 03 Jan 2018 10:36:31 -0500 In-reply-to: (message from Stefan Monnier on Tue, 02 Jan 2018 22:24:57 -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:221551 Archived-At: > From: Stefan Monnier > Date: Tue, 02 Jan 2018 22:24:57 -0500 > > Also we need to "interpret" the ChangeLog guidelines in the context of > tools such as vc-region-history where we don't need to look through the > ChangeLog just to know when a given piece of code was modified. Let's not forget that we don't always have access to a VCS. Moreover, sometimes you are looking for information that is not easily gleaned from Git history. One example is establishing whether some change was in Emacs XX.YY or in a later version. Given our messy DAG and Git's general indifference to branch-specific history, I find the ChangeLog's in the tarball a better tool for this job.