[prev in list] [next in list] [prev in thread] [next in thread] 

List:       haiku-bugs
Subject:    Re: [Haiku-bugs] [Haiku] #3491: Create fields for GCC version,
From:       "nielx" <trac () haiku-os ! org>
Date:       2009-02-27 17:04:15
Message-ID: 050.c0efc0632bbc99ea37851d763944d720 () haiku-os ! org
[Download RAW message or body]

#3491: Create fields for GCC version,  kernel-version, and hardware type
--------------------------+-------------------------------------------------
 Reporter:  mmadia        |       Owner:  haiku-web     
     Type:  enhancement   |      Status:  new           
 Priority:  normal        |   Milestone:  R1            
Component:  Website/Trac  |     Version:  R1 development
Blockedby:                |    Platform:  All           
 Blocking:                |  
--------------------------+-------------------------------------------------

Comment(by nielx):

 Replying to [comment:2 anevilyak]:
 > Actually, I would disagree there: I can think of quite a few bugs of
 varying severity that only show up on gcc4 builds, so it would be quite
 helpful to be able to filter the bugs by applicable compiler, though the
 keywords mechanism you mentioned would probably do the trick there ;
 however, that somewhat relies on people being uniform in their keyword
 usage to be truly helpful when trying to categorize.

 The advantage with the keyword approach is that when you query for gcc4,
 you are certain that you will find gcc4 related bugs, and not all the bugs
 that happen to be reported on a gcc4 compiled image.

 We can make keyword handling uniform by creating a list of accepted
 keywords and maintaining these.

-- 
Ticket URL: <http://dev.haiku-os.org/ticket/3491#comment:3>
Haiku <http://dev.haiku-os.org>
The Haiku operating system.
_______________________________________________
Haiku-bugs mailing list
Haiku-bugs@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/haiku-bugs
[prev in list] [next in list] [prev in thread] [next in thread]