Hi, 2010/3/29 Rob Hamerling <[email protected]>: > > Contributions should be run through validation by the contributor himself > before committing. The tools are available to anyone. Code which does not > validate should be put aside. > We all prefer to do better things than cleaning up other people's 'dirty' > code. > Well... we could consider to clean it up when it does not happen too often. However, I am in general reluctant to modify 'other peoples' code and it often is more complex then changing a header or some casing. It is about samples, about division of library and application code etc. So yes, we need to be more strict on commiting core code. And also, we might have an 'inbox' where non-compliant code can be dropped and anyone can take these and make them compliant. Would it be possible to put this inbox on the group, so no write access to svn is required?
Joep -- You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jallib?hl=en.
