I seem to be in a love/hate relationship with Git. On the one hand, it’s… well, horrible, usability wise, with all it’s unexpected behaviors and weird terminology for well known concepts. On the other hand, it does nice things like this when changes are committed:
...
rename noodil.py => kit_library/hello.py (71%)
mode change 100755 => 100644
rewrite noodil.py (95%)
...
What I had here was one file, noodil.py, which was an initial piece of executable test code. Moving on a bit, I wanted to make the main executable a wrapper that could run other code, with the initial test code becoming a hello.py demo script. The way I accomplished this was to copy noodil.py to kit_library/hello.py, remove the few startup/teardown lines, and then in the noodil.py file, leave essentially JUST those startup/teardown lines. A little bit of extra editing was done to each file, of course.
Anyway, that “rename (71%) and rewrite (95%)” is a pretty good summary of what happened. The mode change too, is there indicating that I copied the file, but that it’s no longer executable in its new location (actually I saved a second copy from my editor). It’s probably nothing much more than a per-line checksum, but this stuff really does give an impression of git understanding and tracking my work at a high-level. I’m impressed 
For what it’s worth, Noodil is my fledgling python project to bring a combination of Unix pipes, Automator, Powershell, and other tools to the GUI in a new way. More on that later, when I have something useful to demonstrate — other than the unquestionably useful Hello World, of course
