Coding standards: Related bug workarounds

Matej Urbas matej.urbas at
Wed Mar 17 07:14:20 PDT 2010


I hope you don't mind me asking something like this here, but is there a
coding guideline for referencing bugs in related projects for which we
have to do a 'temporary' workaround in our project?

Here is a description of what I mean -- using a (hypothetical) example: 

int a = getSomeNumber(); 
// WA: We have to do something crazy because of a bug in some other
// project:
// [WABUG:] 
while (a < 10) { 
a = getSomeOtherNumber(); 

Thus, the format of the so-called 'Workaround Bug' would be: 


Checking for fixed/referenced WABUGs could be automated easily and
everyone would be happy.

Do we have anything like that?

Thank you,
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
URL: <>

More information about the xorg-devel mailing list