Suggestions for ChangeLog: cut it, and start config/ChangeLog

[Stan Shebs]

Hans-Peter Nilsson wrote:
> 
> Subject says it most.
> 
> 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.

GDB has been cutting ChangeLogs at year boundaries for quite a while, and
that seems to work well.  If you know the year of a change, you can go straight
to the right file.  Also, ChangeLogs at the beginning of a year are especially
quick to update!

> 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".

That doesn't seem like such a good idea; very often changes in generic code
are associated with changes to config/ code, so if you're researching history,
you'll have to have both ChangeLogs up at the same time - which defeats the
purpose of making them separate.

Stan