| 1 |
1.3.2006, 11:29:47, Danny van Dyk wrote: |
| 2 |
|
| 3 |
>> > | Where is a coding style problem related to quality of code in general |
| 4 |
>> > | and assurance in particular? > > It's more relevant than you might |
| 5 |
>> think. Screwing up layout like that > breaks various QA checking tools |
| 6 |
>> that assume that things are in the > standard format. |
| 7 |
>> |
| 8 |
>> A tool that chokes on coding style (like tabs and whitespaces) should be |
| 9 |
>> ifself fixed. |
| 10 |
> Hmm, you never used repoman, right? repoman checks for whitespace and tab |
| 11 |
> oddities and warns you, if you want to commit them. |
| 12 |
|
| 13 |
|
| 14 |
Sure I did... that's not the breakage of a QA tool ciaranm has been talking |
| 15 |
about, though. If some tool stops to work b/c of spacing/indenting issues, |
| 16 |
then it's broken. Meanwhile, if you can't bear formating/whitespace issues, |
| 17 |
then either fix it yourself or file a bug and wait until someone gets to it |
| 18 |
or fixes it when next revbump/another bunch of more important fixes is due. |
| 19 |
|
| 20 |
Expecting that someone will fix a cosmetic issue within five minutes from |
| 21 |
the time when a bug is filed and ranting about it on #gentoo-qa and mailing |
| 22 |
lists isn't useful but rather plain annoying. |
| 23 |
|
| 24 |
-- |
| 25 |
|
| 26 |
jakub |
Archives