On 2011/04/07 02:03, Ingo Schwarze wrote: > Hi Paul, > > Paul Irofti wrote on Thu, Apr 07, 2011 at 02:44:52AM +0300: > > > Of course this goes to the mailinglist instead of the commit log. > > Should we start okaying commit messages from now on as well?! > > Dont't panic! > > In case you agree (in this case, with martynas@) that a commit message > is exceptionally misleading and likely to cause serious confusion in > the future, you can use > > cvs admin -mREV:MSG FILE > > in addition to the clarifying mail to fix the message in CVS as well. > This is not git, you know, where they consider unfixability of wrong > commit messages a feature. ;-) > > However, be very careful, don't damage the repo while fiddling > around with cvs admin. In particular, specify the correct FILE > and revision. > > Yours, > Ingo >
For something which really needs to go in the log, a forced commit is far safer.
