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, 12 Jan 2018 10:21:53 +0200 Message-ID: <83wp0n32se.fsf@gnu.org> References: <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> <7c7503b4-1f82-8a25-fedd-c61c3e7629f6@cs.ucla.edu> <83zi5o6w4p.fsf@gnu.org> <745d2f02-8ca3-8962-0de4-053340c8fa63@cs.ucla.edu> <83efmx6862.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1515745260 25329 195.159.176.226 (12 Jan 2018 08:21:00 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 12 Jan 2018 08:21:00 +0000 (UTC) Cc: emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jan 12 09:20:56 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 1eZua3-0005yk-KG for ged-emacs-devel@m.gmane.org; Fri, 12 Jan 2018 09:20:51 +0100 Original-Received: from localhost ([::1]:53112 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eZuc3-0007af-Ag for ged-emacs-devel@m.gmane.org; Fri, 12 Jan 2018 03:22:55 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:54863) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eZubR-0007aE-Ba for emacs-devel@gnu.org; Fri, 12 Jan 2018 03:22:18 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eZubN-0005jn-CF for emacs-devel@gnu.org; Fri, 12 Jan 2018 03:22:17 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:36519) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eZubN-0005ji-90; Fri, 12 Jan 2018 03:22:13 -0500 Original-Received: from [176.228.60.248] (port=3635 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1eZubM-0006KM-Ms; Fri, 12 Jan 2018 03:22:13 -0500 In-reply-to: (message from Stefan Monnier on Thu, 11 Jan 2018 17:08:51 -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:221872 Archived-At: > From: Stefan Monnier > Date: Thu, 11 Jan 2018 17:08:51 -0500 > > FWIW, I think we should design the system for the case where the > user *does* have the VCS history at hand. We already do that. > It's perfectly OK for someone to decide to hack on Emacs starting from > a tarball rather than from a Git tree, but then this user gets what he > asked for. Since I'm frequently in that situation, I don't want to be disadvantaged like that, especially since keeping the ChangeLog files nowadays means a barely tangible effort from the project. IOW, the color of this particular bike shed can stay as it is, without anyone being unnecessarily at a disadvantage.