On Wed, 2014-04-09 at 12:03 +0200, Jakub Jelinek wrote: > Another issue is bad toplevel ChangeLog entries. > 2014-04-04 Bill Schmidt <wschm...@linux.vnet.ibm.com> > > Backport from mainline > 2013-11-22 Ulrich Weigand <ulrich.weig...@de.ibm.com> > > * libgo/config/libtool.m4: Update to mainline version. > * libgo/configure: Regenerate. > > 2013-11-17 Ulrich Weigand <ulrich.weig...@de.ibm.com> > > * libgo/config/libtool.m4: Update to mainline version. > * libgo/configure: Regenerate. > > 2013-11-15 Ulrich Weigand <ulrich.weig...@de.ibm.com> > > * libtool.m4: Update to mainline version. > * libjava/libltdl/acinclude.m4: Likewise. > > * gcc/configure: Regenerate. > * boehm-gc/configure: Regenerate. > * libatomic/configure: Regenerate. > * libbacktrace/configure: Regenerate. > * libffi/configure: Regenerate. > * libgfortran/configure: Regenerate. > * libgomp/configure: Regenerate. > * libitm/configure: Regenerate. > * libjava/configure: Regenerate. > * libjava/libltdl/configure: Regenerate. > * libjava/classpath/configure: Regenerate. > * libmudflap/configure: Regenerate. > * libobjc/configure: Regenerate. > * libquadmath/configure: Regenerate. > * libsanitizer/configure: Regenerate. > * libssp/configure: Regenerate. > * libstdc++-v3/configure: Regenerate. > * lto-plugin/configure: Regenerate. > * zlib/configure: Regenerate. > > Except for the libtool.m4 change, which is a toplevel change, all > those changes are to files in subdirectories which have their own ChangeLog > file (or in case of libjava/classpath ChangeLog.gcj), the ChangeLog entries > should go into those directories rather than the toplevel ChangeLog.
Ah, right. I had meant to fix this before committing the patch set and dropped the ball. One question: Where are ChangeLog entries supposed to go for libgo? There doesn't seem to be any kind of ChangeLog file for that component. Thanks, Bill > > Jakub >