On 10/6/06, Paul Vriens <[EMAIL PROTECTED]> wrote:
For example, if something is marked as a BUG then I'd expect the person
that marked it, to follow up (either by a patch, by chasing somebody to
look into this, or to create a bugzilla entry). He/she has spent already
some time looking into this
On 10/6/06, Paul Vriens <[EMAIL PROTECTED]> wrote:> > Say, has anybody posted a summary of the Coverity reports lately?> > e.g. how many issues it flagged in Wine, and how many have been examined?
> > http://scan.coverity.com/ is the only place I know of.OK, I just logged in there and scraped the t
On Fri, 2006-10-06 at 00:35 -0700, Dan Kegel wrote:
> On 10/6/06, Paul Vriens <[EMAIL PROTECTED]> wrote:
> > On the other hand, several annotations are from April (6 months
> > development since) and several bugs have been fixed already (but of
> > course not seen).
>
> Say, has anybody posted a s
On 10/6/06, Paul Vriens <[EMAIL PROTECTED]> wrote:
On the other hand, several annotations are from April (6 months
development since) and several bugs have been fixed already (but of
course not seen).
Say, has anybody posted a summary of the Coverity reports lately?
e.g. how many issues it flag
On Thu, 2006-10-05 at 23:55 -0700, Dan Kegel wrote:
> On 10/5/06, Paul Vriens <[EMAIL PROTECTED]> wrote:
> > the email sent by Coverity also asks for a 'main contact'. Do we have
> > such a person already?
>
> Not that I know. Are you volunteering?
If nobody steps up, sure.
>
> > Can we give t
On 10/5/06, Paul Vriens <[EMAIL PROTECTED]> wrote:
the email sent by Coverity also asks for a 'main contact'. Do we have
such a person already?
Not that I know. Are you volunteering?
Can we give them a date when they could recreate the database?
Maybe it's good to have a clean start on this
On Thu, 2006-10-05 at 16:02 -0700, Dan Kegel wrote:
> Coverity has to reset their database soon to recover from a
> database problem (the one that's keeping new scans from showing up).
>
> Somebody should probably scrape the Wine results from the Coverity
> database soon so we can avoid losing any
Coverity has to reset their database soon to recover from a
database problem (the one that's keeping new scans from showing up).
Somebody should probably scrape the Wine results from the Coverity
database soon so we can avoid losing any annotations we care about...
- Dan
