http://bugzilla.kernel.org/show_bug.cgi?id=8066
------- Additional Comments From [EMAIL PROTECTED] 2007-03-14 15:03 ------- Yes. The protocols is this: OPEN a bug when a failure in Linux is sighted. ASSIGN a bug report when it is acknowledged and somebody is at least trying to look into it. RESOLVE a bug report when there is a patch in the report available to test. CLOSE a bug report when the symptom in upstream Linux is gone. So this bugzilla reflects the state of Linux -- not necessarily the state of ACPICA. Of course, if the fix was somehow incomplete and there are additional Linux sightings that may be related to the same cause, then we'll see additional Linux bug reports opened. This is also why issues that are fixed first in ACPICA may hang around in the RESOLVED state for some time -- as they are waiting for the ACPICA fix to make it into Linux before they are CLOSED. ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
