GNU bug report logs - #27953
vc-region-history doesn't follow renames

Previous Next

Full log

Message #40 received at 27953-done <at> debbugs.gnu.org (full text, mbox):

From: Kyle Meyer <kyle <at> kyleam.com>
To: Clément Pit--Claudel <clement.pitclaudel <at> live.com>
Cc: Andreas Schwab <schwab <at> linux-m68k.org>,
 Stefan Monnier <monnier <at> IRO.UMontreal.CA>, 27953-done <at> debbugs.gnu.org
Subject: Re: bug#27953: vc-region-history doesn't follow renames
Date: Sat, 05 Aug 2017 16:55:57 -0400

Clément Pit--Claudel <clement.pitclaudel <at> live.com> writes:

> On 2017-08-05 19:05, Kyle Meyer wrote:

[...]

>> But you shouldn't need to add --follow here.  Renames should be followed
>> by default when -L is used.  (At least, that's what I see using Git
>> v2.13.3.)
>
> This seems to be new. Adding --follow appears to make git follow renames here (2.7.4).

OK, just to check with a concrete example: When you run

  git log -L37,57:test/lisp/ls-lisp-tests.el 9df49cddae

565cfd9f6 isn't listed as the earliest commit?

When I run that with Git 2.8.5 (and 2.13.3), I see 565cfd9f6 as the
earliest commit, indicating that Git does detect the rename
(test/lisp/ls-lisp.el => test/lisp/ls-lisp-tests.el).  I wasn't able to
try with your version, 2.7.4, because I couldn't get it to build.

-- 
Kyle

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.