From: "dan carpenter" <error27@email.com>
To: greg@kroah.com
Cc: linux-kernel@vger.kernel.org, smatch-discuss@lists.sourceforge.net
Subject: Re: smatch update / 2.5.64 / kbugs.org
Date: Thu, 06 Mar 2003 03:15:29 -0500 [thread overview]
Message-ID: <20030306081529.28620.qmail@email.com> (raw)
From: Greg KH <greg@kroah.com>
> What I really need to know is, what are all of the reported errors in a
> specific portion of the kernel tree. If you give some way to search
> based on filename and path, I think you will find a lot more people
> using the results of this tool. I know I would :)
>
You are right of course... I'll do that tomorrow evenning. :)
> Also, what advantage does signing up for a user account on the kbugs.org
> site give you?
>
I'm glad you asked. When you log in then you can moderate
the bugs as a bug or not a bug. I am going to make that
more obvious, by adding "Login to moderate" next to each
bug when you look at the source.
Tracking bug moderations from one version to the next is
basically working since 2.5.63.
thanks,
dan carpenter
--
_______________________________________________
Sign-up for your own FREE Personalized E-mail at Mail.com
http://www.mail.com/?sr=signup
Meet Singles
http://corp.mail.com/lavalife
next reply other threads:[~2003-03-06 8:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-06 8:15 dan carpenter [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-07 8:32 smatch update / 2.5.64 / kbugs.org dan carpenter
2003-03-07 6:45 dan carpenter
2003-03-07 6:53 ` Oleg Drokin
2003-03-14 8:25 ` Oleg Drokin
2003-03-06 7:37 dan carpenter
2003-03-06 7:42 ` Greg KH
2003-03-06 15:37 ` Oleg Drokin
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=20030306081529.28620.qmail@email.com \
--to=error27@email.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=smatch-discuss@lists.sourceforge.net \
/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