From c9049e20ffc4cd7b85325dc58c9893d9d57e3a5c Mon Sep 17 00:00:00 2001 From: Oliver Tale-Yazdi Date: Fri, 25 Aug 2023 15:33:42 +0200 Subject: [PATCH] Update commit hash after history-rewrite Signed-off-by: Oliver Tale-Yazdi --- substrate/.git-blame-ignore-revs | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/substrate/.git-blame-ignore-revs b/substrate/.git-blame-ignore-revs index c99a3070231d8..aae391d6d8351 100644 --- a/substrate/.git-blame-ignore-revs +++ b/substrate/.git-blame-ignore-revs @@ -10,6 +10,6 @@ # # You should add new commit hashes to this file when you create or find such big # automated refactorings while reading code history. If you only know the short hash, -# use `git rev-parse 1d5abf01` to expand it to the full SHA1 hash needed in this file. +# use `git rev-parse 7b56ab15b4` to expand it to the full SHA1 hash needed in this file. -1d5abf01abafdb6c15bcd0172f5de09fd87c5fbf # Run cargo fmt on the whole code base (#9394) +7b56ab15b4a8e06df5eefc17e600e3c1419aede5 # Run cargo fmt on the whole code base (#9394)