I was talking about both some type of revision control or configuration
management in addition to a bug tracking program like GNATS, or the
comercial product, ClearDDTs.
: to "finalize". Although something major like "skbuffs" or "dentries"
: rarely seems to be "backed down from", and the actual "forgot to i++"
: type patches don't really affect documentation.
Right, a lot of patches today are simply bug fixes (typos, misc. things,
etc.) that don't cause any change to the design of the subsystem. A
simple change log would be the only type of documentation necessary
for this type of change.
This would be useful in order to attempt to track when defects were
entered into the source tree.