GNU bug report logs - #26345
25.1; vc-annotate in Git is unable to fully navigate the history if the file was moved

Previous Next

Full log

Message #20 received at 26345 <at> debbugs.gnu.org (full text, mbox):

From: Dmitry Gutov <dgutov <at> yandex.ru>
To: Wojciech Siewierski <wojciech.siewierski <at> gmail.com>, 26345 <at> debbugs.gnu.org
Subject: Re: bug#26345: 25.1; vc-annotate in Git is unable to fully navigate
 the history if the file was moved
Date: Mon, 1 May 2017 04:41:04 +0300

On 15.04.2017 2:46, Wojciech Siewierski wrote:

>> Hmm, you're right. It does, however, improve the following scenario:
>>
>> C-x v g, j, p, n
>>
>> I.e. you can move between revisions belonging to the old file name
>> (with the next/previous commands), just not between different file names.

> Right, I missed that but you're right. That's definitely a massive
> improvement. Thanks!

I've pushed that patch now. Keeping this bug open because it doesn't fix 
the main scenario.

For future reference (mine or someone else's): when we reach the end of 
the revision list for a particular file name, we can call 'git show REV 
-M' to look for the next file name, a simple example here: 
https://kparal.wordpress.com/2011/08/03/git-tip-of-the-day-detect-moved-files/.

Previous Next

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