mirror of
https://github.com/lwip-tcpip/lwip.git
synced 2025-01-26 09:35:23 +00:00
doc: contrib: CVS -> Git, punctuation fixes
This commit is contained in:
parent
b9b31a5e72
commit
74939c20c4
@ -34,7 +34,7 @@ features of Savannah help us not lose users' input.
|
|||||||
2.3 Bug reports and patches:
|
2.3 Bug reports and patches:
|
||||||
|
|
||||||
1. Make sure you are reporting bugs or send patches against the latest
|
1. Make sure you are reporting bugs or send patches against the latest
|
||||||
sources. (From the latest release and/or the current CVS sources.)
|
sources. (From the latest release and/or the current Git sources.)
|
||||||
2. If you think you found a bug make sure it's not already filed in the
|
2. If you think you found a bug make sure it's not already filed in the
|
||||||
bugtracker at Savannah.
|
bugtracker at Savannah.
|
||||||
3. If you have a fix put the patch on Savannah. If it is a patch that affects
|
3. If you have a fix put the patch on Savannah. If it is a patch that affects
|
||||||
@ -46,14 +46,13 @@ features of Savannah help us not lose users' input.
|
|||||||
4. Do not file a bug and post a fix to it to the patch area. Either a bug report
|
4. Do not file a bug and post a fix to it to the patch area. Either a bug report
|
||||||
or a patch will be enough.
|
or a patch will be enough.
|
||||||
If you correct an existing bug then attach the patch to the bug rather than creating a new entry in the patch area.
|
If you correct an existing bug then attach the patch to the bug rather than creating a new entry in the patch area.
|
||||||
5. Patches should be specific to a single change or to related changes.Do not mix bugfixes with spelling and other
|
5. 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
|
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
|
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.
|
if it's not to the point and long :) so the chances for it to be applied are greater.
|
||||||
|
|
||||||
2.4 Platform porters:
|
2.4 Platform porters:
|
||||||
|
|
||||||
1. If you have ported lwIP to a platform (an OS, a uC/processor or a combination of these) and
|
1. If you have ported lwIP to a platform (an OS, a uC/processor or a combination of these) and
|
||||||
you think it could benefit others[1] you might want discuss this on the mailing list. You
|
you think it could benefit others[1] you might want discuss this on the mailing list. You
|
||||||
can also ask for CVS access to submit and maintain your port in the contrib CVS module.
|
can also ask for Git access to submit and maintain your port in the contrib Git module.
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user