From: Matthew Wilcox <willy@debian.org>
To: kernel-janitors@vger.kernel.org
Subject: Re: [Kernel-janitors] [RFT] Update to the mandocs build target
Date: Tue, 20 Apr 2004 12:09:57 +0000 [thread overview]
Message-ID: <20040420120957.GG18329@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <40831B29.9010108@stillhq.com>
[-- Attachment #1: Type: text/plain, Size: 1148 bytes --]
On Tue, Apr 20, 2004 at 05:44:19PM +1000, Michael Still wrote:
> Another interesting problem is that of repeated comments. There are
> places where more than one comment documents a function of a given name.
> At the moment the last found comment wins. Ultimately it would be nice
> to audit those comments, and work out why there are repeats (multiple
> architectures repeating code?).
Architectures should not be including kerneldoc comments. i386 is and
always has been the refereence platform for Linux and thus is the only
architecture which should have kerneldoc comments. If there's one thing
worse than having one set of buggy comments, it's having eight sets of
buggy comments, all subtly incompatible.
--
"Next the statesmen will invent cheap lies, putting the blame upon
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince
himself that the war is just, and will thank God for the better sleep
he enjoys after this process of grotesque self-deception." -- Mark Twain
[-- Attachment #2: Type: text/plain, Size: 167 bytes --]
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/kernel-janitors
prev parent reply other threads:[~2004-04-20 12:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-19 0:19 [Kernel-janitors] [RFT] Update to the mandocs build target Michael Still
2004-04-19 22:23 ` Randy.Dunlap
2004-04-20 7:44 ` Michael Still
2004-04-20 12:09 ` Matthew Wilcox [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040420120957.GG18329@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=kernel-janitors@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.