This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
The use of the toplevel ChangeLog and config/ChangeLog
- From: Kelley Cook <kcook34 at ford dot com>
- To: gcc at gcc dot gnu dot org, gdb at sources dot redhat dot com, binutils at sources dot redhat dot com
- Date: Fri, 29 Aug 2003 10:45:00 -0400
- Subject: The use of the toplevel ChangeLog and config/ChangeLog
- Hop-count: 1
- Reply-to: Kelley Cook <kelleycook at wideopenwest dot com>
[Crossposted to the GCC, GDB, and Binutils mailing lists]
A recent checkin by Daniel Jacobowitz to the config directory called my
attention to an apparent anomaly in the ChangeLogs for the config/
directory.
Some checkins to the config directory are accompanied by an addition to
the config/ChangeLog:
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/config/ChangeLog?sortby=date&only_with_tag=MAIN
While other checkins are being documented in the toplevel ChangeLog with
a config/xxxx: entry:
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/ChangeLog?sortby=date&only_with_tag=MAIN#rev1.795
Since this is confusing, I propose two alternatives:
a) There remains a separate config/ChangeLog and all the config/ changes
be documented only in there.
b) All changes to the config/ directory be documented in the toplevel
directory and there not be a config/ChangeLog.
Of course, it is quite possible, that am I missing something and there
is a reason that some go in one ChangeLog and some in the other?
Anyway I'll volunteer to clean up the ChangeLog(s), if everyone can come
to an agreement of which way it should go. Personally, I would think
that the ChangeLog in the toplevel should be good enough.
Kelley Cook