LLVM Bugzilla is read-only and represents the historical archive of all LLVM issues filled before November 26, 2021. Use github to submit LLVM bugs

Bug 12 - what happened to UNCONFIRMED
Summary: what happened to UNCONFIRMED
Status: RESOLVED INVALID
Alias: None
Product: Bugzilla Admin
Classification: Unclassified
Component: UI (show other bugs)
Version: unspecified
Hardware: PC Linux
: P normal
Assignee: Misha Brukman
URL:
Keywords: invalid-bug
Depends on:
Blocks:
 
Reported: 2003-10-07 16:44 PDT by Brian R. Gaeke
Modified: 2010-02-22 12:50 PST (History)
2 users (show)

See Also:
Fixed By Commit(s):

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Brian R. Gaeke 2003-10-07 16:44:07 PDT 
I thought when we enter bugs into the database, they were supposed
to show up as "UNCONFIRMED" until someone went to the trouble of
confirming them. It seems to be true, at least, if you believe
http://zion/bugs/bug_status.html . Instead they seem to be
showing up as NEW or ASSIGNED, I'm not sure which.
Comment 1 Chris Lattner 2003-10-10 00:24:56 PDT 
Is there some advantage of UNCONFIRMED over NEW that I'm not seeing?  I'm
thinking this is "not a problem", things just show up as NEW, not unconfirmed.
Comment 2 Brian R. Gaeke 2003-10-10 17:11:45 PDT 
yeah, now that i think about it, it's not really a bug, it's just something from
the documentation that confused me, I guess.

I think the right answer may be, if you set "Number of votes a bug in this
product needs to automatically get out of the UNCONFIRMED state:" to 0 as it is
by default, then all bugs are NEW, not UNCONFIRMED.

RESOLVED INVALID because Brian didn't look at the prefs hard enough the first
time. :-)