tags:

views:

3464

answers:

44

Following this topic, what is the best (as in witty and/or funny) commit message you have ever encountered?

For example, here's the message for a commit I made a few minutes ago:

This change should have never been made. It kills little children.
NOTE TO SELF: Don't do everything [the boss] tells you immediately.

+40  A: 

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

GameFreak
*cringe*. grudging +1
TokenMacGuy
+6  A: 

Bug 1920 -- Embarassing Lack of Thorough Testing

Scott Porad
+10  A: 

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

"Sorry I forgot to add the files"

levhita
I do that all the time :)
Andrei Taranchenko
Im glad git allows me to fix commits I get wrong like this. Other scms should follow this pattern.
TokenMacGuy
Mercurial allows you to do that too.Had to do this just yesterday :-)
Johannes Rudolph
+2  A: 

"This will fix the bug"

Vijay Dev
+5  A: 

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

+83  A: 
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."
SquareCog
These are pretty much paraphrases of a sequence of emails I sent out to a webdev team a few weeks ago when I was struggling with a form input encoding problem... ugh.
Andrew Heath
+24  A: 

"No changes made"

danimajo
I've had to do that. It's usually best to comment why the checkin was necessary anyway.
Joshua
which is usually followed by a list of 10 files all with changes.
Ray Booysen
I typically do "interim checkin" in my local SVK branch 10-20 times, before I push a major feature update back to the main repo. My merge commit message is usually pretty thorough, tho.
Chris Kaminski
+27  A: 

To those I leave behind, good luck!

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

Terence Lewis
You shouldn't be allowed to commit code on your last day.
Bill the Lizard
Sounds like a good time to revert...
David Zaslavsky
<vcs of choice> diff
Chris Kaminski
+4  A: 

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.

Joshua
+1  A: 

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

01
+17  A: 

The best public one i've encountered is probably this xkcd reference 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).
Henrik Gustafsson
+5  A: 

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.

Gunnar Steinn
You mean you had spacey workers? <G>
Loren Pechtel
The smartass version of this being, `svn ci -m "\\0"`
ojrac
+1  A: 

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

r123: F#[email protected]
Orion Edwards
+3  A: 

"Will this work?"

Matthias van der Vlies
+3  A: 

This is my favorite: ""

Andrew Hare
The .NET port of this commit message is string.Empty
mmsmatt
+7  A: 

I like "Friday 5pm"

Andomar
+1  A: 

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."

Jason Baker
+5  A: 

"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. :)

Paulius Maruška
+3  A: 

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

Refactoring

harto
You'd probably be even more annoyed when I commit a change commented by "Refactored Mercilessly!"
TokenMacGuy
A: 

I found these -

Another version

More code

Final version

Bhushan
+16  A: 

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&amp;view=markup

This has simply *got* to be a literary reference, but I don't know from what...anyone?
Beska
+8  A: 

"Going skydiving this weekend."

+10  A: 

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.

Mark Simpson
Never going to give you up...Never let you down...Never gonna run around and desert you.
Michael Kniskern
It was actually a can of coke.
Krougan
+7  A: 

"I'm sorry."

Andrei Krotkov
+8  A: 

From the StackOverflow repository:

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

tghw
I'll assume the names were changed to protect the innocent?
Kieveli
http://www.youtube.com/watch?v=MlfcF1I5e_g
Jarrod Dixon
+6  A: 

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"

NascarEd
+13  A: 

"Changed tabs to 4 spaces."

gridzbi
Haha, I've collaborated with a friend on something and I use 2 spaces for indentation, and he uses tabs. Each time the files were passed back and forth they were reindented by each of us.
The Wicked Flea
I would flip out of I saw this commit message. If you really want to treat the indents as spaces, configure your editor to do that with tabs behind the scenes. don't change every line in the file...
rmeador
A: 

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

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

Wyatt Barnett
+68  A: 

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       |
             *|     *  *  *      | *
    _________)/\\_//(\/(/\)/\//\/|_)_______
Joe White
Oh God, my soda is all over the monitor...
Sorin Comanescu
The consultant shouldn't be spending his time/your money with ASCII art ;)
Aardvark
Given how much it's improved our code, it's worth the time spent on the ASCII art.
Joe White
That's ace. :)
Mark Simpson
+6  A: 

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.

+2  A: 

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?

David Brown
+1 for the office space references. -1 for pointing them out.
Oorang
The question was sarcasm, because I knew I wouldn't *need* to point the references out. :P
David Brown
+16  A: 

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

I guess patience must truly be a virtue.
Michael Foukarakis
+19  A: 

Tyop fix.

Yes, just like that.

Robert Munteanu
+2  A: 

Regarding some comments in the source code:

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

Adam Rosenfield
+5  A: 

Removed curse words from the code

Ryu
+1 I've seen the exact same one from my old system architect (i think he changed "fucked up" to "screwed up" in a comment
Viktor Sehr
+2  A: 

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

Roberto Aloi
+3  A: 

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
San Jacinto
+1  A: 

Seen, and believed:

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

Michael Foukarakis
+1  A: 

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

Tikhon Jelvis
A: 
//This is wrong. This is so wrong...
Julio Montoya
+5  A: 

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

Roberto Aloi
Lol, but is this a real one?
bobobobo
A: 
Commit 

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

dagofly
+2  A: 

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

changed the old code to new code

tsps