Conversation

Notices

1. Embed this notice
   Friedrich Delgado ✔️🎀 (taupan@mastodon.social)'s status on Wednesday, 20-Nov-2024 20:43:25 JST Friedrich Delgado ✔️🎀

   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.

   #git #python

   1/

   • Embed this notice
     Peter Krefting (nafmo@social.vivaldi.net)'s status on Wednesday, 20-Nov-2024 20:43:25 JST Peter Krefting

     in reply to

     @TauPan When I need to do something like that, and "git log --follow -p -C -C -M" doesn't work, I resort to "git gui blame" on the file, and look at where things are introduced, and then use the "show history context" to look at the change and "blame parent commit" to find the code as it was previous to continue searching backwards.