| |||||||||||||
2.6.32.9 Release notes2.6.32.9 Release notesPosted Feb 23, 2010 11:59 UTC (Tue) by NAR (subscriber, #1313)In reply to: 2.6.32.9 Release notes by vonbrand Parent article: 2.6.32.9 Release notes You fix it, and go your merry way chasing the next bug. Or you then sit down trying to organize the whole mess to create an intelligible commit message/impact assesment. Better skip the second part, as it slows down the fixing of bugs. No, the job of the software developer is not only to fix bugs, but create useful commit messages, because somebody else might look at the same code a couple of years later and would like to know why that change was introduced.
(Log in to post comments)
2.6.32.9 Release notes Posted Feb 23, 2010 13:23 UTC (Tue) by hppnq (guest, #14462) [Link] No, the job of the software developer is not only to fix bugs, but create useful commit messages, because somebody else might look at the same code a couple of years later and would like to know why that change was introduced. There is a fundamental difference between a commit message that accurately describes what was fixed (which is not dependent on any other context than the code that was touched), and an assessment of the impact of that fix in what could be a huge range of contexts, most of which have little or nothing to do with the actual implementation.
Not knowing how and when to distinguish between these two is what makes these
|
|||||||||||||