Best development practices state that you should keep your changeset comments meaningful. Comments like “another small fix” or “HTML updated” or (empty comment) aren’t very descriptive. I’ve even discovered that using ticket number (“fixes #4”) as a comment is neither good idea (it may happen that you will decouple your repository browser from issue tracker, like I did, when started using Warehouse).
Though lots of developers don’t write descriptive comments on changesets or do it rarely. I am not an exception — I have this sin, too. Some of my comments have no real sense. For years, I was lazy enough to not to read svn book or to google a bit. Now I’ve decided to spend that 10 minutes, and voila — now I can update my comments when they are already made. That’s pretty simple.
First of all, make sure you have copied repo/hooks/pre-revprop-change.tmp to repo/hooks/pre-revprop-change (or just created simple `exit 0’ sh script with this name) and made it executable.
Then you could do something like:
$ svn propset svn:log --revprop -r <REVISION> "My corrected log message" <URL>
# or
$ svn propset svn:log --revprop -r <REVISION> -F <file-with-corrected-log-message.txt> <URL>
# or
$ svn propedit svn:log --revprop -r <REVISION>
If you use Warehouse, you fill find that first of all, it does not syncs it automatically, so you have to copy that post-commit hook behavior to pre-revprop-change or run it manually. Though 1.0.4 doesn’t work well with that kind of changes (it will not sync them), so you have to apply this patch
Setting up warehouse instead of trac soon, so that patch will come in handy!