On Wed, 2010-03-17 at 20:42 -0400, Gaetan Nadon wrote: > On Wed, 2010-03-17 at 14:14 +0000, Matej Urbas wrote: > > 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? > > > Not to my knowledge. I checked the GNU coding standards but could not > find anything.
Thanks for checking. I have sent a proposal for this to bug-standa...@gnu.org. Cheers, --- Matej
signature.asc
Description: This is a digitally signed message part
_______________________________________________ xorg-devel@lists.x.org: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: http://lists.x.org/mailman/listinfo/xorg-devel
