Loading docs/CONTRIBUTE +25 −26 Original line number Diff line number Diff line Loading @@ -243,21 +243,20 @@ 3.4 How to get your changes into the main sources 1. Submit your patch to the curl-library mailing list Submit your patch to the curl-library mailing list. 2. Make the patch against as recent sources as possible. Make the patch against as recent sources as possible. 3. Make sure your patch adheres to the source indent and coding style of already existing source code. Failing to do so just adds more work for me. Make sure your patch adheres to the source indent and coding style of already existing source code. Failing to do so just adds more work for me. 4. Respond to replies on the list about the patch and answer questions and/or fix nits/flaws. This is very important. I will take lack of replies as a sign that you're not very anxious to get your patch accepted and I tend to simply drop such patches from my TODO list. Respond to replies on the list about the patch and answer questions and/or fix nits/flaws. This is very important. I will take lack of replies as a sign that you're not very anxious to get your patch accepted and I tend to simply drop such patches from my TODO list. 5. If you've followed the above mentioned paragraphs and your patch still hasn't been incorporated after some weeks, consider resubmitting it to the list. If you've followed the above paragraphs and your patch still hasn't been incorporated after some weeks, consider resubmitting it to the list. 3.5 Write good commit messages Loading Loading
docs/CONTRIBUTE +25 −26 Original line number Diff line number Diff line Loading @@ -243,21 +243,20 @@ 3.4 How to get your changes into the main sources 1. Submit your patch to the curl-library mailing list Submit your patch to the curl-library mailing list. 2. Make the patch against as recent sources as possible. Make the patch against as recent sources as possible. 3. Make sure your patch adheres to the source indent and coding style of already existing source code. Failing to do so just adds more work for me. Make sure your patch adheres to the source indent and coding style of already existing source code. Failing to do so just adds more work for me. 4. Respond to replies on the list about the patch and answer questions and/or fix nits/flaws. This is very important. I will take lack of replies as a sign that you're not very anxious to get your patch accepted and I tend to simply drop such patches from my TODO list. Respond to replies on the list about the patch and answer questions and/or fix nits/flaws. This is very important. I will take lack of replies as a sign that you're not very anxious to get your patch accepted and I tend to simply drop such patches from my TODO list. 5. If you've followed the above mentioned paragraphs and your patch still hasn't been incorporated after some weeks, consider resubmitting it to the list. If you've followed the above paragraphs and your patch still hasn't been incorporated after some weeks, consider resubmitting it to the list. 3.5 Write good commit messages Loading