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 #17 received at 26345 <at> debbugs.gnu.org (full text, mbox):

From: Wojciech Siewierski <wojciech.siewierski <at> gmail.com>
To: Dmitry Gutov <dgutov <at> yandex.ru>, 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: Sat, 15 Apr 2017 01:46:32 +0200

[Message part 1 (text/plain, inline)]

On 11.04.2017 01:25, Dmitry Gutov wrote:
> On 10.04.2017 18:06, Wojciech Siewierski wrote:
>
>> The error is gone but usability-wise not much has changed: now the
>> vc-annotate buffer contains "fatal: no such path olddir/file.txt in
>> master" after I finish my test scenario.
>
> 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.
>
>> I guess not much more can be done.
>
> It probably can, but someone would have to work out the exact sequence
> of Git commands to do what we want.
Right, I missed that but you're right. That's definitely a massive
improvement. Thanks!

[signature.asc (application/pgp-signature, attachment)]

Previous Next

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