> On Wed, 29 Nov 1995, Nick Andrew wrote:
>
> > How about logging recent changes in the comment at the top of the source
> > file and removing older changes after some time has passed? That will
> > prevent the source files from growing without bound and will also
> > provide some documentation of code changes over time.
>
> Do you mean spread the change log out over all the files it effects?
> That would be a maintenance nightmare. Keep the change logs together in
> one easy to search and maintain location. If you have to go hunting
> through the source for comments about what was changed, you might as well
> look through the patches.
If they were put there, then someone would collect and put them on a
web site somewhere :-)
However, I like the idea - as others have suggested - of a Change.log
file in the base directory of the kernel sources. Easy to find, easy
to maintain, everyone gets a copy, and changes to the file will
describe the changes to the kernel, AND the current changes are also
documented as diffs to this file in the patches themselves!
Basically, all Linus will have to do is add his announcements and
comments to this file for each new version, and then as usual diff to
create the patch.
To start the process off, all that is needed is a collection of all the
previous announcements to be put together and included in the current
sources to be added as a new file in a forthcoming patch. Easy.
Problem solved? :)
Cheers
Tony
-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-
T.Nugent@sct.gu.edu.au tnugent@cit.gu.edu.au tonyn@sctnugen.ppp.gu.edu.au
-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-
A former California inmate is suing his jailers because they refused to
provide him dental floss. He said he got cavities because he could not floss.