romenskiy2012/curl
1
0
Fork 0
mirror of https://github.com/curl/curl.git synced 2026-08-25 11:33:33 +03:00
Code Issues Projects Releases Packages Wiki Activity

various changes of CVS to git

Browse source
This commit is contained in:
Daniel Stenberg 2010-03-22 00:34:09 +01:00
parent e1d6034977
commit 1609685fc2
8 changed files with 34 additions and 33 deletions
Download patch file Download diff file Expand all files Collapse all files

27
docs/CONTRIBUTE
View file

@ -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
==============================================================================
@ -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
@ -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
@ -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