Then "cloister bell <cloister@hhhh.org>" wrote:
>i have to disagree with that. comments in the code should *not* be
>wrong; certainly not horribly so. if the point of having comments is to
>help people understand the kernel, then adding incorrect comments can
>only hurt that effort.
I believe that Russ was implying that someone with a "more than minimal"
knowledge of the sections of code they were commenting would be submitting
the comments. I don't think that commenting should be the *complete*
domain
of the programmer working on the code. In any event, if someone does start
putting comments in they might stumble across a logic bug or make finding
them easier.
Later, Cloister said: "[...] but i wouldn't submit kernel comment
patches unless you have good reasons for thinking they're correct. if
there are issues you're unclear about, ask about them here before
finalizing your patch. [...]"
VERY TRUE! Since everyone getting this E-mail should have access
to reply to comments, it would probably be a great place to start asking.
If things get too long winded, we could always start another mailing list
for kernel comments -- Kernel Komments? :) At any rate, Russ has made
very good comment: "Linus does a good job of weeding out the cruft."
I would propose having one/two central people for a comment organizer
and then let them submit the comments to Linus.
Dan
****************************************************************
* Dan Linder - Inacom :: National System Support Center
* SCO ACE, Compaq SCO UNIX ASE
****************************************************************