Samuel Tardieu <[EMAIL PROTECTED]> writes: > As a recent committer to GCC, I am always surprised to see the content > of ChangeLog entries and commit messages. > > I tend to find GCC ChangeLog entries useless. For example, the more > recent ChangeLog entry in gcc/ChangeLog is: > > | 2007-11-30 Jan Hubicka <[EMAIL PROTECTED]> > | > | * ggc-common.c (dump_ggc_loc_statistics): Reset ggc_force_collect > | flag. > > How could a newcomer guess why the gcc_force_collect flag needs to be > reset?
That is supposed to be written in a comment. The change log entry should describe _what_ is being changed, so that you can find out when a particular change was made. Andreas. -- Andreas Schwab, SuSE Labs, [EMAIL PROTECTED] SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."
