Coding standards: Related bug workarounds

[Matej Urbas]

Hi,

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:https://bugzilla.redhat.com/show_bug.cgi?id=527510] 
while (a < 10) { 
a = getSomeOtherNumber(); 
} 

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

[WABUG:<uri>]

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

Do we have anything like that?

Thank you,
---
Matej
-------------- 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: <http://lists.x.org/archives/xorg-devel/attachments/20100317/c5d00914/attachment.pgp>