The Creating a patch section of the Documentation Project: Subversion page contains a list of 4 items. This list did not survive the switch to Markdown and now displays as 4 lists of 1 empty element each. List items with line/paragraph breaks are not Markdown's strength, but I am pretty sure there is a way to do it.
Note that the last step says to "Send email to the docs@httpd.apache.org". Sending patches to a mailing list should be a very last resort. If someone chooses to contribute via patches, there is much less risk that their patches will be lost by adding them to a ticket. But if they choose to send directly to the docs mailing list, they must be aware that messages are rejected (or possibly just lost) unless the mail is “sent from an @apache.org address or a subscriber address or an address in LDAP” (as reported in ticket #27).
🅭🄍
The Creating a patch section of the Documentation Project: Subversion page contains a list of 4 items. This list did not survive the switch to Markdown and now displays as 4 lists of 1 empty element each. List items with line/paragraph breaks are not Markdown's strength, but I am pretty sure there is a way to do it.
Note that the last step says to "Send email to the docs@httpd.apache.org". Sending patches to a mailing list should be a very last resort. If someone chooses to contribute via patches, there is much less risk that their patches will be lost by adding them to a ticket. But if they choose to send directly to the
docsmailing list, they must be aware that messages are rejected (or possibly just lost) unless the mail is “sent from an @apache.org address or a subscriber address or an address in LDAP” (as reported in ticket #27).🅭🄍