That's a good way to hurt yourself ;)

I religiously apologise to my team when I screw up :)

Others do not, which is why they need some (electrically) induced motivation.

Well played with the comment though :)

Even better grab a random Linus response to Linux kernel commits and add it as a comment. Example: [GitUser], SHUT THE FUCK UP!

It's a bug alright - in the [GitRepo]. How long have you been a maintainer? And you still haven't learnt the first rule of [GitRepo] maintenance?

If a change results in user programs breaking, it's a bug in the [GitRepo]. We never EVER blame the user programs. How hard can this be to understand?

Good idea. Also comments from theo.c in mg:

http://www.openbsd.org/cgi-bin/cvsweb/src/usr.bin/mg/theo.c?...

Scroll down a bit to the array...

"We have two kinds of developers - those that deal with their own shit and those that deal with other people's shit.",