generic-library/curl
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

CONTRIBUTE: minor edits

Browse Source 
Slightly modified to become a nicer web page when converted for the site
This commit is contained in:
Daniel Stenberg 2011-03-18 11:14:51 +01:00
parent 92774ac1f3
commit 89d412b5e7
1 changed files with 25 additions and 26 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

51
docs/CONTRIBUTE
View File

@ -233,47 +233,46 @@
For unix-like operating systems: For unix-like operating systems:
http://www.gnu.org/software/patch/patch.html http://www.gnu.org/software/patch/patch.html
http://www.gnu.org/directory/diffutils.html http://www.gnu.org/directory/diffutils.html
For Windows: For Windows:
http://gnuwin32.sourceforge.net/packages/patch.htm http://gnuwin32.sourceforge.net/packages/patch.htm
http://gnuwin32.sourceforge.net/packages/diffutils.htm http://gnuwin32.sourceforge.net/packages/diffutils.htm
3.4 How to get your changes into the main sources 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 Make sure your patch adheres to the source indent and coding style of already
already existing source code. Failing to do so just adds more work for me. 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 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 fix nits/flaws. This is very important. I will take lack of replies as a sign
sign that you're not very anxious to get your patch accepted and I tend to that you're not very anxious to get your patch accepted and I tend to simply
simply drop such patches from my TODO list. drop such patches from my TODO list.
5. If you've followed the above mentioned paragraphs and your patch still If you've followed the above paragraphs and your patch still hasn't been
hasn't been incorporated after some weeks, consider resubmitting it to the incorporated after some weeks, consider resubmitting it to the list.
list.
3.5 Write good commit messages 3.5 Write good commit messages
A short guide to how to do fine commit messages in the curl project. A short guide to how to do fine commit messages in the curl project.
---- start ---- ---- start ----
[area]: [short line describing the main effect] [area]: [short line describing the main effect]
[separate the above single line from the rest with an empty line] [separate the above single line from the rest with an empty line]
[full description, no wider than 72 columns that describe as much as [full description, no wider than 72 columns that describe as much as
possible as to why this change is made, and possibly what things possible as to why this change is made, and possibly what things
it fixes and everything else that is related] it fixes and everything else that is related]
---- stop ---- ---- stop ----
Don't forget to use commit --author="" if you commit someone else's work, Don't forget to use commit --author="" if you commit someone else's work,
and make sure that you have your own user and email setup correctly in git and make sure that you have your own user and email setup correctly in git
before you commit before you commit