We had a class that had been around forever, and that was central to a lot of the work our application did. But the class name was pretty much incomprehensible (and always had been).

One day while I was pairing with a consultant, he convinced me to refactor and give it a sensible, readable name. Here's the commit comment:

Joe & Don -- TBS_Coll is dead. Long live TProjection.

                   ----------
                  /          \
                 /    REST    \
                /      IN      \
               /     PEACE      \
              /                  \
              |     TBS_Coll     |
              |  33809 revisions |
              |    killed by a   |
              |     Level 26     |
              |    consultant    |
              |    wielding a    |
              |     blessed      |
              |  +3 refactoring  |
              |                  |
              |       2006       |
             *|     *  *  *      | *
    _________)/\\_//(\/(/\)/\//\/|_)_______

Rev 53571: "This is a basic implementation that works."
Rev 53572: "By works, I meant 'doesnt work'.  Works now.."
Rev 53573: "Last time I said it works? I was kidding.  Try this."
Rev 53574: "Just stop reading these for a while, ok.. "
Rev 53575: "Give me a break, it's 2am.  But it works now."
Rev 53576: "Make that it works in 90% of the cases.  3:30."
Rev 53577: "Ok, 5am, it works.  For real.  
            Back when I said basic implementation? Scratch that."

I don't know what these changes are supposed to accomplish but somebody told me to make them.

Tyop fix.

Yes, just like that.

To those I leave behind, good luck!

Committed by an ex-employee on his last day of work - the code didn't even compile.

"No changes made"

Look at your commit message, now back to mine. Now back at your message. Now back to mine. Sadly it isn't mine, but if you stopped writing non meaningful commit messages, it could look like mine. Look down, back up, where are you? You're browsing revisions, looking at changes your changes could look like. Did you break the build? Back at my commit message, it's a message saying something you want to hear. Look again at the source code. The source code is now diamonds. Anything is possible when you post meaningful commit messages. I'm on a horse.

Inspired by: http://www.youtube.com/watch?v=owGykVbfgUE

MSVC6 pain:

"COMP: Day 8 of our attempt to compile vtkUnicodeString on MSVC 6. I am increasingly concerned about the expedition's morale -- our cook, Johnson has begun to alternate between sullenness bordering on insubordination and fits of increasing anger. I fear that extreme measures may need to be taken to enforce good order and discipline among the men ..."

http://public.kitware.com/cgi-bin/viewcvs.cgi/Common/vtkUnicodeString.cxx?revision=1.10&view=markup ^[1]

This one: http://github.com/radar/humanize/commit/37882a8dea71672ff86cc77d6e0bbfccfdbf1bd6

The best public one i've encountered is probably this ^[1] xkcd reference ^[2] in the OpenBSD tree resulting in a man-page for msleep(9):

Log message:
<oga> art write me a manpage
<art> What? Write it yourself.
<oga> sudo art write me a manpage.
<art> ok

Document msleep(9).

"Changed tabs to 4 spaces."

just one commit after big commit with a long list coupled changes...

"Sorry I forgot to add the files"

I got rickrolled by a colleague's changelist :/

Another one was "Tell me if you read this". When my friend asked the guy why he'd written it, he got a free mars bar for his efforts.

"I'm sorry."

I once worked with a guy who loved to write code, reams and reams of code. Even if it wasn't necessary, more code was always better. He would crank out a few hundred lines a day or a couple of thousand over a weekend and his commit message was always the same:

"misc"

Removed curse words from the code

I like "Friday 5pm"

From the StackOverflow repository:

changeset 2089:df87fd7fa064
date: Jan 10 2009
author: jdixon
| penis

"Going skydiving this weekend."

I commit they to the land of the free but alas not that free of bugs.

Commit "murder"

Commit-ted to this code I am not but you asked me so there.

I am so Committed!

Commit-ee designed - dont blame me.

The commit-ee made me do it

So long and thanks for the save

Source Code Control to Major Tom

Damn didnt mean to save - but hey at least its in

Its not full of stars Dave... Its not full of stars..

** cries**

the shiney mice made me do it.

Revision: 329109 Author: borgman Date: 10/5/2010 12:40:52 PM Message:

changed the old code to new code

"If you're reading this, I'm screwed..."

My organization puts pre-commit hooks that must be satisfied. You have to specify a bug number to match it up with the bug repo.

One dev., upon reaching bug number 409, put:

She's so fine, my bug #409

My own: Fixed an error in the time space continuum.

The darn thing was behaving as if we had a cache-coherency problem, only there was no cache. Thankfully, I found the bug.

Bug 1920 -- Embarassing Lack of Thorough Testing

The best I've seen is a single space which came very popular at my workplace after the architect put a rule in TFS that you could not check in unless you wrote a comment.

Most annoying (and frequent) one on a recent project:

Refactoring

"Now <insert feature> sorta kinda works."

I just love this one, because it doesn't suggest, that the feature is fully completed. I use it all the time. :)

There was a bug in the desktop module of our software that would do some funky things to phone numbers, so the web module always choked on the data. I wasn't in charge of the desktop module, which meant that my web module wouldn't work correctly until the desktop guy got around to my bug report.

This is my commit message on the web module after waiting for a week or two:

I... I... I didn't receive my bug fix this week. I could set the module on fire...

A couple of days later:

And then the boss told me to talk to development and development told me to talk to the boss and I still haven't received my bug fix and he took my stapler and he never brought it back...

The next day:

Well, Ok. But... that's the last straw.

Can you tell that I'm a major "Office Space" fan?

"Will this work?"

This is my favorite: ""

"This will fix the bug"

Commit 

WTF!! i know you're committing but you're committing what changes exactly ??

"my comp is crashing, HELP!!!!!"

Regarding some comments in the source code:

Removed fuck. [Project name] is now a 2-f project!

I will compile the code before committing. I will compile the code before committing. I will...

I've seen my share of the ever-popular:

r123: F#$@

I've decided to stop posting commit messages saying "x is finished." Why? Because it never really is finished and I don't notice that one stupid little change I forgot to make until after I've committed.

This applies also if I make another change that says "ok, now x is really finished."

Seen, and believed:

my code for handling checksum of odd sized packets was rubbish. Fixed.

I remember seeing a whole series of commits where the comments all--in addition to useful information--told a story about squirrels.

Commit messages coming from http://whatthecommit.com/

And for those who'd like to be lazy and use SVN:

svn ci -m "`curl -s 'http://whatthecommit.com/' | grep '<p>' | cut -c4-`"

//This is wrong. This is so wrong...

This is in the SAGEPAY .php example files. It really instilled confidence that their payment service is secure!

The SimpleXor encryption algorithm NOTE: This is a placeholder really. Future releases of VSP Form will use AES or TwoFish. Proper encryption This simple function and the Base64 will deter script kiddies and prevent the "View Source" type tampering It won't stop a half decent hacker though, but the most they could do is change the amount field to something else, so provided the vendor checks the reports and compares amounts, there is no harm done. It's still more secure than the other PSPs who don't both encrypting their forms at all

One of my staff entered all his commit messages simply as "edit website" for about a week before I noticed him doing it.

When all hope was lost and I had prayed that this would be the last commit to fix the problem I made this comment (in Greek):

Κύριε Ἰησοῦ Χριστέ, Υἱὲ τοῦ Θεοῦ, ἐλέησόν με τὸν ἁμαρτωλόν.

Lord Jesus Christ, have mercy on me, a sinner. An equivalent of, "DEAR GOD, PLEASE MAKE THIS WORK... PLEEEEAASE"

I found these -

Another version

More code

Final version

Just saw this gem: Re-adding stuff to SVN after SVNFart.

I've completely forgot what SVNFart was . . . .

I'm a newbie at git (just learnt it few days ago). One of the most frequent commit messages was Compile errors fixed! before i understood that it was something wrong and read this thread after googling "funny commit messages".Fortunately i used local private git-server :)

"Work that I didn't commit yet.":

https://github.com/mxcl/threepanes/commit/f33db26585b1bb51c2e2578f00c2f9b44748137d