Lines Matching refs:to

6 2 How to contribute to lwIP
8 Here is a short list of suggestions to anybody working with lwIP and 
9 trying to contribute bug reports, fixes, enhancements, platform ports etc.
11 to fixes or questions might often come late. Hopefully the bug and patch tracking 
24 9. don't initialize static and/or global variables to zero, the compiler takes care of that.
31    (This forces you to synchronize documentation and implementation.)
43    is to NOT touch archs you can't test and let maintainers take care of them.
44    This is a good way to see if they are used at all - the same goes for unix
46 4. Do not file a bug and post a fix to it to the patch area. Either a bug report
48    If you correct an existing bug then attach the patch to the bug rather than creating a new entry in the patch area.
50    can go to the lwip-users list. This is still the fastest way of interaction and the list is not so crowded
51    as to allow for loss of fixes. Putting bugs on Savannah and subsequently closing them is too much an overhead
53 6. Patches should be specific to a single change or to related changes.Do not mix bugfixes with spelling and other
55    change behaviour if not necessary.A patch is easier to read and understand if it's to the point and short than
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.