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: The name gnus-cloud.el Date: Mon, 01 Jan 2018 06:40:29 +0200 Message-ID: <83vagmchtu.fsf@gnu.org> References: <87374jd66s.fsf@lifelogs.com> <87bmj6dda0.fsf@linux-m68k.org> <87vahe911g.fsf@lifelogs.com> <87374id7jy.fsf@linux-m68k.org> <877ett8g7k.fsf@lifelogs.com> <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> <834lo6eoty.fsf@gnu.org> <861sjas8td.fsf@dod.no> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1514781532 10061 195.159.176.226 (1 Jan 2018 04:38:52 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 1 Jan 2018 04:38:52 +0000 (UTC) Cc: emacs-devel@gnu.org To: Steinar Bang Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jan 01 05:38:48 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 1eVrs3-00023j-Iu for ged-emacs-devel@m.gmane.org; Mon, 01 Jan 2018 05:38:43 +0100 Original-Received: from localhost ([::1]:36544 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eVru2-0003Xl-L6 for ged-emacs-devel@m.gmane.org; Sun, 31 Dec 2017 23:40:46 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:41473) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eVrtw-0003Xg-UN for emacs-devel@gnu.org; Sun, 31 Dec 2017 23:40:41 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eVrtt-00007H-PM for emacs-devel@gnu.org; Sun, 31 Dec 2017 23:40:40 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:39532) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eVrtt-00007A-Le; Sun, 31 Dec 2017 23:40:37 -0500 Original-Received: from [176.228.60.248] (port=3131 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1eVrtt-0000i9-1G; Sun, 31 Dec 2017 23:40:37 -0500 In-reply-to: <861sjas8td.fsf@dod.no> (message from Steinar Bang on Mon, 01 Jan 2018 01:48:30 +0100) 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:221495 Archived-At: > From: Steinar Bang > Date: Mon, 01 Jan 2018 01:48:30 +0100 > > >>>>> Eli Zaretskii : > > > I don't understand why this is relevant: since Git doesn't record > > renames, but instead "deduces" them by comparing contents, why should > > it matter how the file was moved? > > It doesn't. > > Where it breaks down is usually where the moved/renamed file is modified > as part of the move commit, so that the hash changes. AFAIK, the file I used as an example wasn't modified as part of the move.