ubuntu-x-swat team mailing list archive

[Geir Ove Myhr <gomyhr@xxxxxxxxx>]

On Sun, Jul 5, 2009 at 6:37 PM, Jeffrey Baker wrote:
> Why are you changing all my tags from "GM965" to "965GM"?  Intel has
> never made a part called the 965GM.

The main reason is consistency. Tags are useful because bug reports
with a similar property gets the same tag. In this case, there are
several other bug reports with the 965gm tag and none with gm965, and
it is nice to click on the 965gm tag and get a list of currently open
bugs reported on 965GM. The idea would be to see which tags are used,
and use them instaed of inventing new and similar ones [1].

But I agree that it is a bit confusing which tag to use for a given
chipset. I "standardized" on 965gm more than half a year ago when
there were a few bug reports with each (and similar for other
chipsets). The main reason for using 965gm is that this is what the
chipset is called in the intel driver. In Xorg.0.log you will see the
line
(--) intel(0): Chipset: "965GM"
and when I was cleaning up the tag structure half a year ago I found
that it was most consistent to use this line as a tag name where
possible (some of those are too long or have invalid tag characters).
The list of what can end up on this line can be found in the source
code: http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/tree/src/i830_driver.c
. The currently used tags for X are listed at
https://wiki.ubuntu.com/X/Tagging . Grepping for GM965 in the source
code gives no hits. I have no idea why it is this way, but I think it
is easier to use what the log files say than what it says on the
package.

[1]: When I started to standardize the tags, the list of bugs would
show all tags used for a package along with the number of bug reports
with that tag. While this was problematic since the list would be a
mile long when the list was for all ubuntu bugs, it was very useful as
a suggestion for what tags to put on a bug report.

-- 
xorg deadlocked after screen fades to black
https://bugs.launchpad.net/bugs/395855
You received this bug notification because you are a member of Ubuntu-X,
which is the registrant for xf86-video-intel.