mirror of
https://github.com/moparisthebest/curl
synced 2024-12-21 07:38:49 -05:00
various changes of CVS to git
This commit is contained in:
Daniel Stenberg
parent
e1d6034977
commit
1609685fc2
2
CHANGES
2
CHANGES
@ -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().
|
||||
|
||||
|
||||
10
README
10
README
@ -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)
|
||||
|
||||
|
||||
@ -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
|
||||
|
||||
|
||||
8
docs/FAQ
8
docs/FAQ
@ -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.
|
||||
|
||||
@ -26,8 +26,8 @@ UNIX
|
||||
|
||||
You probably need to be root when doing the last command.
|
||||
|
||||
If you have checked out the sources from the CVS repository, read the
|
||||
CVS-INFO on how to proceed.
|
||||
If you have checked out the sources from the git repository, read the
|
||||
GIT-INFO on how to proceed.
|
||||
|
||||
Get a full listing of all available configure options by invoking it like:
|
||||
|
||||
|
||||
@ -12,9 +12,9 @@ INTERNALS
|
||||
|
||||
The largest amount of code and complexity is in the library part.
|
||||
|
||||
CVS
|
||||
GIT
|
||||
===
|
||||
All changes to the sources are committed to the CVS repository as soon as
|
||||
All changes to the sources are committed to the git repository as soon as
|
||||
they're somewhat verified to work. Changes shall be commited as independently
|
||||
as possible so that individual changes can be easier spotted and tracked
|
||||
afterwards.
|
||||
@ -436,10 +436,10 @@ Memory Debugging
|
||||
information about what they just did. The logged data can then be analyzed
|
||||
after a complete session,
|
||||
|
||||
memanalyze.pl is the perl script present only present in CVS (not part of the
|
||||
release archives) that analyzes a log file generated by the memory tracking
|
||||
system. It detects if resources are allocated but never freed and other kinds
|
||||
of errors related to resource management.
|
||||
memanalyze.pl is the perl script present in tests/ that analyzes a log file
|
||||
generated by the memory tracking system. It detects if resources are
|
||||
allocated but never freed and other kinds of errors related to resource
|
||||
management.
|
||||
|
||||
Internally, definition of preprocessor symbol DEBUGBUILD restricts code which
|
||||
is only compiled for debug enabled builds. And symbol CURLDEBUG is used to
|
||||
@ -483,6 +483,6 @@ Building Releases
|
||||
need to fill in the Makefile.am files properly for which files that should
|
||||
be included in the release archives.
|
||||
|
||||
NOTE: you need to have curl checked out from CVS to be able to do a proper
|
||||
NOTE: you need to have curl checked out from git to be able to do a proper
|
||||
release build. The release tarballs do not have everything setup in order to
|
||||
do releases properly.
|
||||
|
||||
2
maketgz
2
maketgz
@ -1,6 +1,6 @@
|
||||
#! /bin/sh
|
||||
# Script to build release-archives with. Note that this requires a checkout
|
||||
# from CVS and you should first run ./buildconf and build curl once.
|
||||
# from git and you should first run ./buildconf and build curl once.
|
||||
#
|
||||
#***************************************************************************
|
||||
# _ _ ____ _
|
||||
|
||||
Loading…
Reference in New Issue
Block a user