This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Suggestions for ChangeLog: cut it, and start config/ChangeLog
- To: Hans-Peter Nilsson <hp at bitrange dot com>
- Subject: Re: Suggestions for ChangeLog: cut it, and start config/ChangeLog
- From: Jeffrey A Law <law at cygnus dot com>
- Date: Wed, 15 Mar 2000 20:00:48 -0700
- cc: gcc at gcc dot gnu dot org
- Reply-To: law at cygnus dot com
In message <Pine.BSF.4.10.10003152053340.11806-100000@dair.pair.com>you write
:
> The gcc/ChangeLog is now larger than any previous one, adding to "cvs up"
> delay when local changes are made, for one reason.
> Perhaps cutting a ChangeLog.2 at Jan 1 would be good; it would slice off
> 5/7 roughly.
Trimming the ChangeLog on occasion is a good thing. I believe the plan was
to trim it for each major release. So now might not be the best time since
we haven't started the next major release cycle yet.
> I'd also like to propose having a config/ChangeLog, for port changes and
> other config/* changes.
> Maybe that has been discussed and rejected at some time, though I don't
> remember it and no valid hits turned up when searching for "ChangeLog and
> config".
I think this would be a major mistake.
The reason you get no hits is policy for ChangeLogs in gcc -- for reasons I
never fully understood we do not write "config" in the filename for the
ChangeLog entry.
jeff