thanks guys, i think i got through. it was pretty complicated, there weren't any controls over syntax previously, so every change would bring up errors about whitespaces, syntax of "if" statements, etc. i guess its a one time things.
what i found pretty annoying was the 100 char per line limit... i had mnemotechnic names, which were long sometimes, and had to cut them off the get through jenkins. why the 100 char limit? is it some standard i don't know about? the first time i pushed an email was sent to the list with the patch. after the fixes nothing else was sent. the fixes are all syntax stuff. do i have to do something to get the latest version of the patch on the list or should people just look at the first version? (next time i'll go through the check script *before* sending, and avoid this) thanks! On Sat, Nov 19, 2011 at 11:38 PM, Spencer Oliver <[email protected]> wrote: > On Nov 20, 2011 2:37 AM, Rodrigo Rosa wrote: >> >> i'm still having a hard time with a bunch of syntax style stuff, which >> was ok a while ago. >> i committed some stuff and it's complaining about code that is already >> on the master branch... >> i would like to be able to check this stuff on my pc, so i get less >> iterations with jenkins >> >> it there some script to config my compiler to complain about >> everything jenkins checks? >> thanks! >> > > tools/checkpatch.sh from the src tree. > > This is the same checkpatch script run by the build server. > > Cheers > Spen > -- Rodrigo. ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
