PHP Wiki

cvs2svnconversion

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2017/09/22 13:28		current
Line 389:		Line 389:
	</code>		</code>

-	Whew. That was going to make for a //very// long options file where it was very easy to make copypasta errors. I needed to add a little Python code. How does one do foreach (array(//blah blah blah//) as $item) { /* etc / } in Python? So I went to my wife Sarah,* who does know Python.	+	Whew. That was going to make for a //very// long options file where it was very easy to make copypasta errors. I needed to add a little Python code. How does one do foreach (array(//blah blah blah//) as $item) { /* etc / } in Python? So I went to a close friend* who does know Python.

	We came up with this rather handy little bit of code:		We came up with this rather handy little bit of code:

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2009/07/13 04:08		current
Line 13:		Line 13:
	* The daily "[[http://darkrainfall.org/changelog.tar.gz\|changelog]]" script needs to be updated to use SVN		* The daily "[[http://darkrainfall.org/changelog.tar.gz\|changelog]]" script needs to be updated to use SVN
	* README files still reference CVS: README.CVS-RULES, README.QNX, README.RELEASE_PROCESS, README.SUBMITTING_PATCH (hradtke)		* README files still reference CVS: README.CVS-RULES, README.QNX, README.RELEASE_PROCESS, README.SUBMITTING_PATCH (hradtke)
		+
	===== bugs.php.net =====		===== bugs.php.net =====
	* Uses a local copy of CVSROOT/passwd for authentication. Needs to use the API on master. (Jani)		* Uses a local copy of CVSROOT/passwd for authentication. Needs to use the API on master. (Jani)
Line 32:		Line 33:
	===== oti1.php.net =====		===== oti1.php.net =====
	* This windows box (chm builder) needs to be upgraded to use SVN rather then CVS		* This windows box (chm builder) needs to be upgraded to use SVN rather then CVS
		+
		+
		+	===== osu1.php.net ===== (master)
		+	* systems/ updated to use SVN checkout (bjori)
		+	* mirrors/php-master-web/ updated to use SVN checkout (bjori)
		+	* Can't find other CVS checkouts, should be fine now
		+

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2008/07/26 16:45		current
Line 1:		Line 1:
	====== CVS to SVN Migration ======		====== CVS to SVN Migration ======

-	This page will collect all information about the CVS2SVN migration of PHP's cvs.php.net repositories.	+	This page will collect all information about the CVS2SVN migration of PHP's cvs.php.net repositories. Subversion currently seems like a very likely candidate as the future core VCS for PHP. The history has actually already been imported and now the main task is to port all the existing CVS dependent infrastructure.
		+
		+	Mailinglist:
		+	- http://news.php.net/svn.migration
		+
		+	IRC channel:
		+	- #php.svn (EFNet)

	Further information:		Further information:

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2017/09/22 13:28		current
Line 133:		Line 133:
	* You cannot checkout the entire repository on case-insensitive filesystem		* You cannot checkout the entire repository on case-insensitive filesystem
	===== Validating your account =====		===== Validating your account =====
-	To gain access to svn.php.net you have to "validate your SVN account". This is automatically done by logging into master (https://master.php.net/login.php), the wiki (http://wiki.php.net) or reply to bugs on bugsweb (http://bugs.php.net/) from the developer tab.	+	To gain access to svn.php.net you have to "validate your SVN account". This is automatically done by logging into main (https://main.php.net/login.php), the wiki (http://wiki.php.net) or reply to bugs on bugsweb (http://bugs.php.net/) from the developer tab.
	Your access credentials will be synchronized within 15minutes.		Your access credentials will be synchronized within 15minutes.

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2026/04/23 12:23	current
Line 1:	Line 1:
	+	When migrating from CVS to Subversion the following stuff has to be touched (changed/removed/replaced/...)

	+	* scripts in CVSROOT
	+	* cvsclean script in php-src.
	+	* user management (creation/change password)
	+	* snaps building (source and windows)
	+	* release building (similar to snaps...)
	+	* php.net website creation
	+	* doc creation (pear and php)
	+	* *.php.net website publishing
	+	* tiny stuff like "Fixed in CVS" message in the bug tracker
	+	* lxr.php.net
	+	* daily ChangeLog update

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2021/04/06 08:00		current
Line 282:		Line 282:
	===== Github Pull Requests =====		===== Github Pull Requests =====

-	There is a mailing list called <git-pulls@lists.php.net>. All pull requests created for the [[http://github.com/php\|github.com/php]] user will go to this mailing list.	+	As php-src is now hosted on GitHub, you can either use GitHub's UI to merge pull requests, or merge it locally and push it upstream. If you rebase or squash the commits, you can add "Closes GH-1234" to the description of the commit to auto-close the PR.

-	If you have commit rights to a mirrored PHP repository you can pull the requests and push it to the official repositories.	+	See the pull request related sections of the [[gitworkflow#reviewing_and_closing_pull_requests\|Git Workflow]] document for more information.

-	You cannot use the Merge button on GitHub for that. The PHP Organization on GitHub will not accept contributors. It's only for mirroring!	+	There is also a mailing list called <git-pulls@lists.php.net>. All pull requests created for the [[http://github.com/php\|github.com/php]] user will go to this mailing list. The mailing list is less noisy than watching all pull request activity.
-		+
-	See the pull request related sections of the [[gitworkflow#reviewing_and_closing_pull_requests\|Git Workflow]] document for more information.	+

	===== Commit Mails =====		===== Commit Mails =====