Ignore Git's Suspicious Patch Lines
Those who follow me on Twitter have recently been forced to endure a steady stream of rants directed at Git, the DCVS I’ve been trying out while working on the new theme for this site (one really is coming). I’ve only tweeted a fraction of my frustration, but this tweet sums it up nicely:
What the fuck is up with git and its need for precisely zero trailing whitespace?! Suspicious patch lines my ass.
It seems that Git is a finicky little bastard and it pays obscenely close attention to whitespace. If there is a line, any line, with whitespace at the end of it Git decides that something must be fishy. I mean, it’s whitespace. Horror. Everyone knows whitespace is the very spawn of Satan, right? Er, no. Nonetheless, if there’s any trailing whitespace to be found in content that’s being committed, Git balks:
*
* You have some suspicious patch lines:
*The message then proceeds to itemize its suspicions for my viewing pleasure. Tonight I’d finally had enough. I can’t figure out how to make Git force the commit or at least stop it from worrying its pretty little head over a little empty space, so I took drastic measures:
$ sudo chmod a-x /path/to/my/repository/.git/hooks/pre-commit
That’ll teach it to mess with me.
Subscribe3 Comments on Ignore Git's Suspicious Patch Lines