Hm, is there anything that can track the evolution of code in git in a more semantical way?
I happen to have a python codebase that has evolved over almost 13 years. Things that happened:
1/ - Moving from python 2 to python 3 in a `lib/python` code layout, which means that **everything** has moved from `lib/python` to `lib/python3`. Actually `git --follow` can follow the files here, which is helpful.
1/