From: Kelley Cook <kcook34@ford.com>
To: gcc@gcc.gnu.org, gdb@sources.redhat.com, binutils@sources.redhat.com
Subject: The use of the toplevel ChangeLog and config/ChangeLog
Date: Fri, 29 Aug 2003 14:45:00 -0000 [thread overview]
Message-ID: <3F4F66EC.5010407@ford.com> (raw)
[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
next reply other threads:[~2003-08-29 14:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-29 14:45 Kelley Cook [this message]
2003-08-29 17:03 ` Zack Weinberg
2003-08-29 17:46 ` DJ Delorie
2003-08-29 17:42 Nathanael Nerode
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3F4F66EC.5010407@ford.com \
--to=kcook34@ford.com \
--cc=binutils@sources.redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
--cc=kelleycook@wideopenwest.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox