On Sat, Jul 19, 2008 at 09:45:36PM -0700, James G. Sack (jim) wrote: > After some reflection, it dawned on me that my reaction was > unreasonable. To be effective, ChangeLog entries had to be written prior > to the commit --by the committer! So if there was any chance for a > decent CL entry, it could just as well (better, in fact) go in the > commit log. The end result would generally be less effort by the > programmer, and would more likely not be forgotten.
If you want a perfunctury ChangLog just for kicks, may be best to just run a script that generates one from logs. > A further refinement that was suggested, also makes sense to me. Since > some tabulated listings display only the leading N characters of the CL, > it was suggested that the first line of a commit log entry should be > intentionally made a concise summary (containing an issue id, if > relevant), and following lines should be used for detail, where necessary. Perforce does that. cs -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
