On Sat, Jul 19, 2008 at 02:27:10PM -0700, SJS wrote:
BTW, something like "NEWS" which summarizes a bunch of changes in a release
is still useful.
Isn't that what a Changelog file is *for*?
According to the GNU folks, whom as far as I can tell invented the
ChangeLog, or at least defined it, require an entry to the file for every
change. It was basically created before they had any revision control
system. Their developers seem to still behave as if they don't have
revision control. The file is a poor substitute for 'git log', since it
has no correlation with the actual changes themselves.
The NEWS file is a summarized version, kind of like release notes. It's
what you read to find out what is new in this release.
Am I misunderstand the reasons folks use a changelog?
Even finding commented-out code suggests that the programmer thought it
would be too hard to find or retrieve that code later from the revision
control system.
I've yet to see a revision system that is good enough to beat the
utility of commenting out pieces of code. Any system that could
accomplish the same thing would be too complicated to use by folks
who want to code instead of playing with their VCS.
Now, commenting out code and leaving it commented out for long periods
of time... yah. That's not trusting the VCS.
I would say "long periods of time" would be anything more than a few
minutes. Comment it out for a quick test, but if you need to change
something else, commit that change.
I do this all the time with git.
David
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
