spack/.git-blame-ignore-revs

# .git-blame-ignore-revs
# Formatted entire codebase with black 23
603569e321013a1a63a637813c94c2834d0a0023
# Formatted entire codebase with black 22
f52f6e99dbf1131886a80112b8c79dfc414afb7c
black: add .git-blame-ignore-revs toignore black reformatting in blame - [x] add `.git-blame-ignore-revs` to ignore black reformatting - [x] make `spack blame` respect `.git-blame-ignore-revs` (even if the user hasn't configured git to do so) 2022-07-24 18:27:21 -06:00			`# .git-blame-ignore-revs`
Ignore black reformat in git blame (#35544) 2023-02-18 02:03:50 -07:00			`# Formatted entire codebase with black 23`
			`603569e321013a1a63a637813c94c2834d0a0023`
			`# Formatted entire codebase with black 22`
black: fix `.git-blame-ignore-revs` commit A GitHub rebase merge seems to rewrite commits even if it would be a fast-forward, which means that the commit merged from #24718 is wrong. - [x] update `.git-blame-ignore-revs` with real commit from `develop` 2022-07-31 15:13:15 -06:00			`f52f6e99dbf1131886a80112b8c79dfc414afb7c`