Amend committing in SVN

Amending, in Git, is one of my favourite features: it basically lets you modify your local history ( unpushed ) to correct mistakes. Or, more often, to add the missing file.

Obviously, in SVN there isn’t something like the amend, and we’re forced to double-commit to send an atomic and consistent software ( merged with our last changes ).

I’ve seen lot of devs, in amend situations, committing with messages like:

or leaving the message blank, or, worse, repeating the commit message.

None of these types of messages are significant.

Why?

Repeating commit messages drives other people nuts, while leaving blank messages can be a bad practice others in the team do. Although it’s an ugly practice we need to differentiate.

Explicative messages, suck the the two on the list above, are a waste of time: our last commit message was already describing the whole changes, although we forgot to phisically add/delete files or whatever.

So, SVNers, add a message like amend or amend r:64 to your amends, nothing more!


Hi there! I recently wrote an ebook on web application security, currently sold on leanpub, the Amazon Kindle store and gumroad.

It contains 160+ pages of content dedicated to securing web applications and improving your security awareness when building web apps, with chapters ranging from explaining how to secure HTTP cookies with the right flags to understanding why it is important to consider joining a bug bounty program.

Feel free to skim through some of the free chapters published on this blog and, if the content seems interesting enough to you, grab a copy on leanpub, the Amazon Kindle store, gumroad or simply checkout right down below!

Buy the Web Application Security ebook for $9.99

In the mood for some more reading?

...or check the archives.