While poking a SHA-256 hash repository, was surprised to find gitk would fail with a fatal error when called, hence this series. Sending as an RFC, since I am not a git-gui or gitk user, and so while this fixes the original issue and allows me to call gitk to see the branch merge history (which is usually as much as I do with it), it is likey missing some changes, as most of them where found by lightly poking at all of the gui menus (except for remote or tool) It could also be reordered to reduce unnecessary churn and of course also needs the gitk change[1] that was sent independently, and better commit messages. [1] https://lore.kernel.org/git/20211011114723.204-1-carenas@xxxxxxxxx/ Carlo Marcelo Arenas Belón (4): blame: prefer null_sha1 over nullid and retire later rename all *_sha1 variables and make null_oid hash aware expand regexp matching an oid to be hash agnostic track oid_size to allow for checks that are hash agnostic git-gui.sh | 30 ++++++++++++++++-------------- lib/blame.tcl | 18 +++++++++--------- lib/checkout_op.tcl | 4 ++-- lib/choose_repository.tcl | 2 +- lib/commit.tcl | 3 ++- lib/remote_branch_delete.tcl | 2 +- 6 files changed, 31 insertions(+), 28 deletions(-) -- 2.33.0.1081.g099423f5b7
