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: Emacs-diffs Digest, Vol 175, Issue 8 Date: Thu, 01 Jun 2017 20:44:21 +0300 Message-ID: <83lgpbd2mi.fsf@gnu.org> References: <83o9u7dbsh.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1496339404 490 195.159.176.226 (1 Jun 2017 17:50:04 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Thu, 1 Jun 2017 17:50:04 +0000 (UTC) Cc: eric@ericabrahamsen.net, emacs-devel@gnu.org To: Philippe Vaucher Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jun 01 19:49:55 2017 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 1dGUEM-00089X-KE for ged-emacs-devel@m.gmane.org; Thu, 01 Jun 2017 19:49:54 +0200 Original-Received: from localhost ([::1]:46027 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dGUES-0002q4-2i for ged-emacs-devel@m.gmane.org; Thu, 01 Jun 2017 13:50:00 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:48724) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dGU8u-0006ko-VT for emacs-devel@gnu.org; Thu, 01 Jun 2017 13:44:17 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dGU8q-0002E2-DG for emacs-devel@gnu.org; Thu, 01 Jun 2017 13:44:17 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:59297) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dGU8q-0002Dw-Aw; Thu, 01 Jun 2017 13:44:12 -0400 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:2152 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1dGU8p-0005G5-Ai; Thu, 01 Jun 2017 13:44:12 -0400 In-reply-to: (message from Philippe Vaucher on Thu, 1 Jun 2017 17:37:11 +0200) 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:215386 Archived-At: > From: Philippe Vaucher > Date: Thu, 1 Jun 2017 17:37:11 +0200 > Cc: Eric Abrahamsen , Emacs developers > > Is this renaming really necessary? If it isn't, I'd prefer not to > rename, as doing so makes digging into history harder. > > Hum, `git log` has `--follow` which works quite well and `git blame` tracks content changes anyway (not file > names). > The only "gotcha" when renaming a file is to avoid changing its contents as well, otherwise it makes detection > more difficult. Yes, some Git commands can follow renaming, but others cannot, at least not easily. For example, "git log -L" has problems when it crosses the renaming. I had more trouble with other commands, which I cannot at the moment recall; at the very least one needs to use unusual syntax or non-default options which are hard to remember, so that gets in the way when you have the least time. So renaming is okay if we really have to do that, but we shouldn't do it just because we can.