rasmus Mon, 13 Jul 2009 19:15:58 +0000
ViewVC URL: http://svn.php.net/viewvc?view=revision&revision=284024
--- php/php-src/branches/PHP_5_2/INSTALL 2009-07-13 18:14:34 UTC (rev
+++ php/php-src/branches/PHP_5_2/INSTALL 2009-07-13 19:15:58 UTC (rev
@@ -386,7 +386,7 @@
http://snaps.php.net/php5-latest.tar.gz or download binaries for
* a prerelease version downloadable from http://qa.php.net/.
- * you have always the option to obtain PHP through anonymous CVS.
+ * you have always the option to obtain PHP through SVN.
These versions of PHP are compatible to Apache 2.0.40 and later.
@@ -1303,8 +1303,8 @@
When building PHP modules, it's important to have known-good versions
of the required tools (autoconf, automake, libtool, etc.) See the
- Anonymous CVS Instructions for details on the required tools, and
- required versions.
+ SVN Instructions for details on the required tools, and required
Downloading PECL extensions
@@ -1320,14 +1320,11 @@
PECL extensions that have releases listed on the PECL web site are
available for download and installation using the pecl command.
Specific revisions may also be specified.
- * CVS
- Most PECL extensions also reside in CVS. A web-based view may be
- seen at http://cvs.php.net/pecl/. To download straight from CVS,
- the following sequence of commands may be used. Note that phpfi is
- the password for user cvsread:
+ * SVN
+ All PECL files reside in SVN. A web-based view may be seen at
+ http://svn.php.net/pecl/. To download straight from SVN, use:
-$ cvs -d:pserver:cvsr...@cvs.php.net:/repository login
-$ cvs -d:pserver:cvsr...@cvs.php.net:/repository co pecl/extname
+$ svn co http://svn.php.net/repository/pecl/<extname>/trunk <extname>
* Windows downloads
Windows users may find compiled PECL binaries by downloading the
--- php/php-src/branches/PHP_5_2/README.SUBMITTING_PATCH 2009-07-13
18:14:34 UTC (rev 284023)
+++ php/php-src/branches/PHP_5_2/README.SUBMITTING_PATCH 2009-07-13
19:15:58 UTC (rev 284024)
@@ -8,11 +8,11 @@
How to create patch?
-We are working with CVS. You need to get CVS source to create a patch
-that we accept. Visit http://www.php.net/anoncvs.php to get CVS
-source. You can check out older versions, but make sure you get
-the default branch (i.e. Do not use -r option when you check out the
+We use Subversion (SVN) for revision control. You need to get the
+source from SVN in order to create a patch. Read
+http://www.php.net/svn.php for help on using SVN. You can check out
+older branches, but make sure you get trunk as well and make your
+patch work there.
Read CODING_STANDARDS file before you start working.
@@ -21,7 +21,7 @@
patch. Read README.TESTING for testing.
After you finish testing your patch, take diff file using
-"cvs diff > your.patch" command.
+"svn diff > your.patch" command.
Read README.TESTING for submitting a test script for your patch. This is
not strictly required, but it is preferred to submit a test script along
@@ -41,27 +41,10 @@
you are patching PEAR. Official module maintainers can be found in
EXTENSIONS file in PHP source.
-If you are new to CVS (Concurrent Versions System), visit
-http://cvshome.org/ for details.
+If you are new to SVN (Subversion), visit
+http://svnbook.red-bean.com/ for details.
-Recommended CVS client settings for creating patch file
-Recommended ~/.cvsrc file setting is:
-update -d -P
-diff -u means:
- -u Use the unified output format.
-With this CVS setting, you don't have to worry about adding/deleting
-newlines and spaces.
Check list for submitting patch
- Did you run "make test" to check if your patch didn't break
@@ -70,10 +53,7 @@
web server error logs when you test your patch?
- Did you build PHP for multi-threaded web servers. (Optional)
- Did you create test script for "make test"? (Recommended)
- - Did you check your patch is unified format and it does not
- contain white space changes? (If you are not using recommended
- cvs setting)
- - Did you update CVS source before you take final patch?
+ - Did you update SVN source before you take final patch?
- Did you read the patch again?
@@ -118,7 +98,7 @@
What happens when your patch is applied?
-Your name will be included together with your email address in the CVS
+Your name will be included together with your email address in the SVN
commit log. If your patch affects end-users, a brief description
and your name might be added to the NEWS file.
Property changes on: php/php-src/branches/PHP_5_2/build/buildcheck.sh
PHP CVS Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php