On Fri, 2005-02-11 at 21:20 +0000, Joseph S. Myers wrote: > On Fri, 11 Feb 2005, Thorsten Glaser wrote: > > > 4) [svn] Get rid of the forced "ChangeLog" entry > > - writing (it's already the changeset's commit message) > > - formatting (can't that be done automagically?) > > - rotating (d'oh) > > > > I've always found the FSF's ChangeLog policy a bit weird > > (for CVS projects - for RCS projects it's understandable). > > ChangeLog files are highly useful for doing a cvs update and then looking > to see what changed recently - without noting the version number > previously had, and that now had, to do a log of just the relevant part. > Similarly they are useful in snapshots and releases. Automatic generation > on checkout or similar doesn't suffice since svn doesn't version the log > messages themselves - although in principle in a system with log messages > being versioned you could allow all people with write access freely to fix > typos in and otherwise correct log messages and derive ChangeLogs from the > log messages at checkout/export.
The log messages are revision properties, so they don't really need to be versioned. [EMAIL PROTECTED]:~/trunk> svn propget --revprop -r HEAD svn:log Comment fix. * include/svn_client.h(svn_client_propget2): Refer to peg_revision->kind, not just peg_revision. [EMAIL PROTECTED]:~/trunk> svn propget --revprop -r 12964 svn:log Spanish translation updated. * subversion/po/es.po: Some translation updates. If you were to edit it, it would overwrite the property for that revision (which is what you want if you fix typos). So you could derive changelogs if you really wanted to. Anyway, the rest of your comment stands, however.
