I'm working on a 15-year old codebase, and I was here from the beginning. I use 'blame' daily to make sense of code - why it was added, for what project, for wh

I'm working on a 15-year old codebase, and I was here from the beginning. I use 'blame' daily to make sense of code - why it was added, for what project, for what feature, to fix what bug, and who added it. It's priceless, and I'm putting off stuff like getting rid of stupid homegrown types instead of standard ones, using clang-format consistently, and migrating to a small, newer probably faster repository format because I don't want to use history. I realize the value of this history is smaller for newcomers to the team. (And Subversion and it's bigger, expensive brother Perforce still make sense for game development - when you don't really want to go wild with branches or remote work, and when you need multi-terabyte-sized repositories and multi-gigabyte single commits.)