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: Sun, 31 Dec 2017 18:54:58 +0200 Message-ID: <838tdiet25.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> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1514739240 14345 195.159.176.226 (31 Dec 2017 16:54:00 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sun, 31 Dec 2017 16:54:00 +0000 (UTC) Cc: emacs-devel@gnu.org To: Steinar Bang Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Dec 31 17:53: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 1eVgrw-0003Jr-Ms for ged-emacs-devel@m.gmane.org; Sun, 31 Dec 2017 17:53:52 +0100 Original-Received: from localhost ([::1]:45075 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eVgtv-0001w8-S3 for ged-emacs-devel@m.gmane.org; Sun, 31 Dec 2017 11:55:55 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:50877) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eVgtE-0001ua-7B for emacs-devel@gnu.org; Sun, 31 Dec 2017 11:55:13 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eVgtB-0004In-5N for emacs-devel@gnu.org; Sun, 31 Dec 2017 11:55:12 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:57091) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eVgtB-0004Ib-1l; Sun, 31 Dec 2017 11:55:09 -0500 Original-Received: from [176.228.60.248] (port=2576 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1eVgtA-0005G1-Ee; Sun, 31 Dec 2017 11:55:08 -0500 In-reply-to: <86608msw0h.fsf@dod.no> (message from Steinar Bang on Sun, 31 Dec 2017 17:27:26 +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:221488 Archived-At: > From: Steinar Bang > Date: Sun, 31 Dec 2017 17:27:26 +0100 > > > I don't like renaming files because that makes some VCS commands fail > > or work less efficiently, and makes forensics much harder and less > > convenient. > > git itself handles history tracking across renames if the first commit > with the new name has the exact same sha1 hash. It does that erratically. E.g., try displaying history of changes of a portion of a file with "git log -L", in a file that was moved (files under subdirectories of doc/ or good examples), and you see it stop at the rename. Same with "git annotate", AFAIR. These are important forensic tools, and when they hit the brick wall of the rename, finding a way of jumping over that wall and continuing whatever investigation you are doing is not easy, sometimes impossible. E.g., I don't know how to cross that line with "git log -L". > Annotate, ie. 'C-x v g' will show changes from across the rename It does? That's not what I see, e.g., with doc/lispref/display.texi: it never shows anything before 2007-09-06, when the file was moved. What am I missing?