Currently, it's a summary, i.e. it lists what changed between the
previous release and the current release, rather than listing every
single change made.
One advantage of the current scheme is that it leaves out "checked in
feature XXX", "fixed feature XXX not to drop core on packets shorter
than 65000 bytes", etc. stuff; it'd just say "feature XXX added",
without including bug fixes and other changes to features new in the
release in question (as opposed to fixes to stuff that was in the
previous release, where the fix is a change between the releases).
If we *do* want a ChangeLog-style log - either instead of, or in
addition to, the current style of CHANGES file (I'd vote for "in
addition to" if we want a ChangeLog-style log; I think of CHANGES files
as release notes, e.g. something more like a NEWS file), there's a
script "cvs2cl" that apparently turns the output of "cvs log" into a
ChangeLog file:
http://www.red-bean.com/cvs2cl/
(I didn't know about it until I saw something on various FreeBSD mailing
lists; perhaps others were already aware of it).
-
This is the TCPDUMP workers list. It is archived at
http://www.tcpdump.org/lists/workers/index.html
To unsubscribe use mailto:[EMAIL PROTECTED]?body=unsubscribe
