From: Sam Ravnborg <sam@ravnborg.org>
To: Stacy Woods <stacyw@us.ibm.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
"Martin J. Bligh" <mbligh@aracnet.com>
Subject: Re: Bugs sitting in the NEW state for more than 28 days
Date: Sat, 14 Jun 2003 21:40:26 +0200 [thread overview]
Message-ID: <20030614194026.GA3733@mars.ravnborg.org> (raw)
In-Reply-To: <3EEA15EC.7080203@us.ibm.com>
On Fri, Jun 13, 2003 at 02:20:28PM -0400, Stacy Woods wrote:
> There are 125 bugs sitting in the NEW state for more than 28 days
>
> 228 Other Other bugme-janitors@lists.osdl.org
> Make pdfdocs/psdocs/htmldoc fail in 2.5.54
Fixed in linus-latest.
Note that the changes to kernel-doc make it spit out warnings for
all parameters in a funtion which is not documented.
A better solution might be to spit out warnings for parameters
documented but not present.
My perl skills did not suffer for this.
The real errors were in one .tmpl files and one .c file,
The other changes in kernel-doc just helped me identifying the root
cause.
> 384 Other Modules bugme-janitors@lists.osdl.org
> 2.5.62 make modules *.ko has no CRC
I cannot provoke this one. Anyone with more details?
Otherwise I would like to have it closed.
> 485 Other Other bugme-janitors@lists.osdl.org
> "make rpm" fails; no kernel-2.5.65/debugfiles.list
Alan Cox checked in a correction that was present in 2.5.66.
I have tried "make rpm" with 2.5.70 with success.
Can be closed.
Sam
next prev parent reply other threads:[~2003-06-14 19:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-13 18:20 Bugs sitting in the NEW state for more than 28 days Stacy Woods
2003-06-14 19:40 ` Sam Ravnborg [this message]
2003-06-14 20:05 ` Jörn Engel
2003-06-14 20:11 ` Jörn Engel
2003-06-14 20:14 ` Sam Ravnborg
2003-06-14 20:20 ` Jörn Engel
2003-07-15 18:59 Stacy Woods
2003-07-16 13:32 ` Alan Cox
2003-08-19 13:30 Stacy Woods
2003-09-19 14:58 Stacy Woods
2003-09-20 11:35 ` Sam Ravnborg
2003-10-24 13:08 Stacy Woods
2003-10-24 18:57 ` Sam Ravnborg
2003-12-04 19:39 Stacy Woods
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=20030614194026.GA3733@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
--cc=stacyw@us.ibm.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).