Comment by speedgoose
Comment by speedgoose 14 hours ago
They probably didn’t care. And having many small commits instead of a big squashed one can be useful when using git bisect for example.
Comment by speedgoose 14 hours ago
They probably didn’t care. And having many small commits instead of a big squashed one can be useful when using git bisect for example.
I like `tig blame` for this. It has a key (comma, maybe?) that pops back to the file just before the change on the highlighted line so you can quickly work your way backwards through non-changes like you describe. It doesn’t deal with renames well, though.
Yeah. I have never in my entire career thought "there are too many commit messages" when doing code archeology, but I have sometimes thought "damn, this commit is huge"