You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
in that file I put the hashes of a few large and useless commits like changing the formatter or mass-renamings, so that they don't show up in git blame. This works with Magit's blame, but it seems like it doesn't group the commits correctly and in the Magit blame view I'll sometimes get a a few lines in a row that are all shown as the same commit, but the line with the commit date and hash is repeated multiple times for lines that should be grouped
me 2019-10-05 12:12 "do stuff, commit A"
def foo():
me 2019-10-05 12:12 "do stuff, commit A"
whatever()
me 2019-10-05 12:12 "do stuff, commit A"
some_other_stuff()
2 + 2
me 2019-10-05 12:12 "do stuff, some other commit B"
return True
me 2019-10-05 12:12 "do stuff, commit A"
--ignore-revs and --ignore-revs-file were added to git blame fairly recently, in Git 2.23
The text was updated successfully, but these errors were encountered:
We get neighboring chunks that are attributed to the same commit because we use the --incremental argument. We could try to merge these chunks again in magit-blame--make-overlays.
I have these lines in
~/.gitconfig
in that file I put the hashes of a few large and useless commits like changing the formatter or mass-renamings, so that they don't show up in
git blame
. This works with Magit's blame, but it seems like it doesn't group the commits correctly and in the Magit blame view I'll sometimes get a a few lines in a row that are all shown as the same commit, but the line with the commit date and hash is repeated multiple times for lines that should be grouped--ignore-revs
and--ignore-revs-file
were added togit blame
fairly recently, in Git 2.23The text was updated successfully, but these errors were encountered: