Is there any way to patch up the git history for cases like this (absolutely not a git expert)? I know that we don’t want to edit history in general, but if there are a set of specific issues liek this, it might be worth a batch change.

~Chad

> On 31Dec, 2017, at 20:42, Eli Zaretskii <eliz@gnu.org> wrote:
> 
>> From: Steinar Bang <sb@dod.no>
>> Date: Mon, 01 Jan 2018 02:05:27 +0100
>> 
>>>>>>> Andreas Schwab <schwab@linux-m68k.org>:
>> 
>>> On Dez 31 2017, Óscar Fuentes <ofv@wanadoo.es> wrote:
>>>> Most likely, the migration tool didn't bother to perform a `git mv
>>>> <from> <to>' and did the equivalent of `cp <from> <to>; git rm <from>;
>>>> git add <to>' instead.
>> 
>>> No, that's exactly the same operation.  The problem is that commit
>>> b8d4c8d0e9 didn't rename anything.
>> 
>> Yep.  This commit only adds that file, and doesn't remove the existing
>> file
> 
> The file was removed in the previous commit.
> 
>> 2007?  Was that still CVS?  Or was that during bazaar?
> 
> It was Bazaar.
> 
>> How did bazaar track renames?
> 
> Bazaar did track renames, but that commit didn't use "bzr mv".
> 
>> How was bazaar renames handled during the conversion to git?
> 
> I have no idea, but you see the results in the Git repository.