A big fan of my work created this rogue video:
https://drive.google.com/file/d/1opveHaukFK8WbQ8wg8b14wuKJsjoOZfO/view
I appreciate the homage, but I can't take credit for it.
It's really quite beautiful, though. I'm using it as part of my evangelism.
Does anyone have any strategies for following git histories past code
reorganizations (see steps #2 and #5 below)?
My typical experience is:
1. Do blame or history on a file
2. Follow it back to the inevitable "convert to tonel"
3. Go to that commit's parent
4. View repo files at that point
5. Fo
