mirror of
https://github.com/lwip-tcpip/lwip.git
synced 2024-12-23 21:14:18 +00:00
more suggestions
This commit is contained in:
parent
f4f717b20a
commit
09aff62b11
@ -8,7 +8,7 @@ features of Savannah help us not lose users' input.
|
||||
|
||||
|
||||
The suggestions:
|
||||
|
||||
- Make sure you are reporting bugs or send patches against the latest sources.That usually means code in CVS
|
||||
- If you think you found a bug make sure it's not already filed in the bugtracker at savannah
|
||||
- If you have a fix put the patch on Savannah. If it's a patch that affects both core and arch specific
|
||||
stuff please separate them so that the core can be applied separately while leaving the other patch 'open'
|
||||
@ -20,6 +20,10 @@ If you correct an existing bug then attach the patch to the bug rather than crea
|
||||
can go to the lwip-users list. This is still the fastest way of interaction and the list is not so crowded
|
||||
as to allow for loss of fixes. Putting bugs on Savannah and subsequently closing them is too much an overhead
|
||||
for reporting a compiler warning fix.
|
||||
- Patches should be specific to a single change or to related changes.Do not mix bugfixes with spelling and other
|
||||
trivial fixes unless the bugfix is trivial too.Do not reorganize code and rename identifiers in the same patch you
|
||||
change behaviour if not necessary.A patch is easier to read and understand if it's to the point and short than
|
||||
if it's not to the point and long :) so the chances for it to be applied are greater.
|
||||
|
||||
For platform porters:
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user