Loading CHANGES +2 −0 Original line number Diff line number Diff line Loading @@ -10,6 +10,8 @@ Daniel Stenberg (21 Mar 2010) - Ben Greear improved TFTP: the error code returning and the treatment of TSIZE == 0 when uploading. - We've switched from CVS to git. See http://curl.haxx.se/source.html Kamil Dudka (19 Mar 2010) - Improved Curl_read() to not ignore the error returned from Curl_ssl_recv(). Loading CVS-INFO→GIT-INFO +0 −0 File moved. View file README +3 −7 Original line number Diff line number Diff line Loading @@ -34,15 +34,11 @@ WEB SITE http://curl.haxx.se/ CVS GIT To download the very latest source off the CVS server do this: To download the very latest source off the GIT server do this: cvs -d :pserver:anonymous@cool.haxx.se:/cvsroot/curl login (just press enter when asked for password) cvs -d :pserver:anonymous@cool.haxx.se:/cvsroot/curl co curl git clone git://github.com/bagder/curl.git (you'll get a directory named curl created, filled with the source code) Loading docs/CONTRIBUTE +15 −12 Original line number Diff line number Diff line Loading @@ -29,9 +29,9 @@ 2.11 Test Cases 3. Pushing Out Your Changes 3.1 Write Access to CVS Repository 3.2 How To Make a Patch 3.3 How to get your changes into the main sources 3.2 How To Make a Patch with git 3.3 How To Make a Patch without git 3.4 How to get your changes into the main sources ============================================================================== Loading Loading @@ -152,7 +152,7 @@ Please try to get the latest available sources to make your patches against. It makes the life of the developers so much easier. The very best is if you get the most up-to-date sources from the CVS repository, but the if you get the most up-to-date sources from the git repository, but the latest release archive is quite OK as well! 2.10 Document Loading @@ -177,16 +177,19 @@ 3. Pushing Out Your Changes 3.1 Write Access to CVS Repository 3.1 Write Access to git Repository If you are a frequent contributor, or have another good reason, you can of course get write access to the CVS repository and then you'll be able to check-in all your changes straight into the CVS tree instead of sending all changes by mail as patches. Just ask if this is what you'd want. You will be required to have posted a few quality patches first, before you can be granted write access. course get write access to the git repository and then you'll be able to push your changes straight into the git repo instead of sending changes by mail as patches. Just ask if this is what you'd want. You will be required to have posted a few quality patches first, before you can be granted push access. 3.2 How To Make a Patch 3.2 How To Make a Patch with git TODO 3.3 How To Make a Patch without git Keep a copy of the unmodified curl sources. Make your changes in a separate source tree. When you think you have something that you want to offer the Loading Loading @@ -214,7 +217,7 @@ http://gnuwin32.sourceforge.net/packages/patch.htm http://gnuwin32.sourceforge.net/packages/diffutils.htm 3.3 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 Loading docs/FAQ +4 −4 Original line number Diff line number Diff line Loading @@ -236,10 +236,10 @@ FAQ supervised in any way by the project. We still get help from companies. Haxx provides web site, bandwidth, mailing lists, CVS server etc and sourceforge.net hosts project services we take advantage from, like the bug tracker. Also again, some companies have sponsored certain parts of the development in the past and I hope some will continue to do so in the future. lists etc and sourceforge.net hosts project services we take advantage from, like the bug tracker. Also again, some companies have sponsored certain parts of the development in the past and I hope some will continue to do so in the future. If you want to support our project, consider a donation or a banner-program or even better: by helping us coding, documenting, testing etc. Loading Loading
CHANGES +2 −0 Original line number Diff line number Diff line Loading @@ -10,6 +10,8 @@ Daniel Stenberg (21 Mar 2010) - Ben Greear improved TFTP: the error code returning and the treatment of TSIZE == 0 when uploading. - We've switched from CVS to git. See http://curl.haxx.se/source.html Kamil Dudka (19 Mar 2010) - Improved Curl_read() to not ignore the error returned from Curl_ssl_recv(). Loading
README +3 −7 Original line number Diff line number Diff line Loading @@ -34,15 +34,11 @@ WEB SITE http://curl.haxx.se/ CVS GIT To download the very latest source off the CVS server do this: To download the very latest source off the GIT server do this: cvs -d :pserver:anonymous@cool.haxx.se:/cvsroot/curl login (just press enter when asked for password) cvs -d :pserver:anonymous@cool.haxx.se:/cvsroot/curl co curl git clone git://github.com/bagder/curl.git (you'll get a directory named curl created, filled with the source code) Loading
docs/CONTRIBUTE +15 −12 Original line number Diff line number Diff line Loading @@ -29,9 +29,9 @@ 2.11 Test Cases 3. Pushing Out Your Changes 3.1 Write Access to CVS Repository 3.2 How To Make a Patch 3.3 How to get your changes into the main sources 3.2 How To Make a Patch with git 3.3 How To Make a Patch without git 3.4 How to get your changes into the main sources ============================================================================== Loading Loading @@ -152,7 +152,7 @@ Please try to get the latest available sources to make your patches against. It makes the life of the developers so much easier. The very best is if you get the most up-to-date sources from the CVS repository, but the if you get the most up-to-date sources from the git repository, but the latest release archive is quite OK as well! 2.10 Document Loading @@ -177,16 +177,19 @@ 3. Pushing Out Your Changes 3.1 Write Access to CVS Repository 3.1 Write Access to git Repository If you are a frequent contributor, or have another good reason, you can of course get write access to the CVS repository and then you'll be able to check-in all your changes straight into the CVS tree instead of sending all changes by mail as patches. Just ask if this is what you'd want. You will be required to have posted a few quality patches first, before you can be granted write access. course get write access to the git repository and then you'll be able to push your changes straight into the git repo instead of sending changes by mail as patches. Just ask if this is what you'd want. You will be required to have posted a few quality patches first, before you can be granted push access. 3.2 How To Make a Patch 3.2 How To Make a Patch with git TODO 3.3 How To Make a Patch without git Keep a copy of the unmodified curl sources. Make your changes in a separate source tree. When you think you have something that you want to offer the Loading Loading @@ -214,7 +217,7 @@ http://gnuwin32.sourceforge.net/packages/patch.htm http://gnuwin32.sourceforge.net/packages/diffutils.htm 3.3 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 Loading
docs/FAQ +4 −4 Original line number Diff line number Diff line Loading @@ -236,10 +236,10 @@ FAQ supervised in any way by the project. We still get help from companies. Haxx provides web site, bandwidth, mailing lists, CVS server etc and sourceforge.net hosts project services we take advantage from, like the bug tracker. Also again, some companies have sponsored certain parts of the development in the past and I hope some will continue to do so in the future. lists etc and sourceforge.net hosts project services we take advantage from, like the bug tracker. Also again, some companies have sponsored certain parts of the development in the past and I hope some will continue to do so in the future. If you want to support our project, consider a donation or a banner-program or even better: by helping us coding, documenting, testing etc. Loading
