Lines Matching full:and

8 Here is a short list of suggestions to anybody working with lwIP and 
11 to fixes or questions might often come late. Hopefully the bug and patch tracking 
19 4. one space between keyword and opening bracket.
20 5. no space between function and opening bracket.
21 6. one space and no newline before opening curly braces of a block.
23 8. spaces surrounding assignment and comparisons.
24 9. don't initialize static and/or global variables to zero, the compiler takes care of that.
29 1. JavaDoc compliant and Doxygen compatible.
31    (This forces you to synchronize documentation and implementation.)
34 2.3 Bug reports and patches:
37    sources. (From the latest release and/or the current CVS sources.)
41    both core and arch specific stuff please separate them so that the core can
43    is to NOT touch archs you can't test and let maintainers take care of them.
46 4. Do not file a bug and post a fix to it to the patch area. Either a bug report
49 5. Trivial patches (compiler warning, indentation and spelling fixes or anything obvious which take…
50 …can go to the lwip-users list. This is still the fastest way of interaction and the list is not so…
51 …as to allow for loss of fixes. Putting bugs on Savannah and subsequently closing them is too much …
53 …ld be specific to a single change or to related changes.Do not mix bugfixes with spelling and other
54 …trivial fixes unless the bugfix is trivial too.Do not reorganize code and rename identifiers in th…
55 …nge behaviour if not necessary.A patch is easier to read and understand if it's to the point and s…
56    if it's not to the point and long :) so the chances for it to be applied are greater. 
60 1. If you have ported lwIP to a platform (an OS, a uC/processor or a combination of these) and
62    can also ask for CVS access to submit and maintain your port in the contrib CVS module.