diff options
| author | Andrzej Warzyński <andrzej.warzynski@arm.com> | 2025-08-10 17:02:35 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-08-10 17:02:35 +0100 |
| commit | 4066d796e9086916afd130e758ac12811ba796ce (patch) | |
| tree | d2b9102501a495d0560709735c09c04b91908172 /llvm/lib/MC/MCDisassembler/MCRelocationInfo.cpp | |
| parent | 6ec0985ad07d68016587353fce715dce73cf1faa (diff) | |
| download | llvm-4066d796e9086916afd130e758ac12811ba796ce.zip llvm-4066d796e9086916afd130e758ac12811ba796ce.tar.gz llvm-4066d796e9086916afd130e758ac12811ba796ce.tar.bz2 | |
Revert "Update .git-blame-ignore-revs for Pack/Unpack move (#152469)" (#152661)
This reverts commit c43c1c0c45fc1ec3fab7abd6e19b318f6468bf28.
Apologies for the noise - I misunderstood how `git blame --ignore-rev`
works. It’s not suitable for large code-move changes and ends up making
`git blame` more confusing rather than cleaner. From the Git
documentation:
> Lines that were changed or added by an ignored commit will be blamed
> on the previous commit that changed that line or nearby lines.
In this case, since so many new lines were added, skipping the commit
causes `git blame` to attribute them to unrelated changes. I had
expected Git to preserve the true origin of the lines while skipping the
move itself - but that is not what happens.
Therefore, I’m reverting this change. Ignoring the commit obscures blame
history rather than improving it.
Diffstat (limited to 'llvm/lib/MC/MCDisassembler/MCRelocationInfo.cpp')
0 files changed, 0 insertions, 0 deletions