Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:39284 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 31838 invoked from network); 25 Jul 2008 00:20:04 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 25 Jul 2008 00:20:04 -0000 Authentication-Results: pb1.pair.com header.from=scott@macvicar.net; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=scott@macvicar.net; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain macvicar.net from 193.227.246.108 cause and error) X-PHP-List-Original-Sender: scott@macvicar.net X-Host-Fingerprint: 193.227.246.108 ip246-108-v193.static.x-ip.net Received: from [193.227.246.108] ([193.227.246.108:48960] helo=lovelace.midden.org.uk) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 57/DA-22699-23C19884 for ; Thu, 24 Jul 2008 20:20:03 -0400 Received: from macvicar.demon.co.uk ([80.177.111.173] helo=[192.168.1.100]) by lovelace.midden.org.uk with esmtpsa (TLS-1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.69) (envelope-from ) id 1KMB2L-0005B8-TY; Fri, 25 Jul 2008 01:20:00 +0100 Cc: PHP Developers Mailing List Message-ID: To: Rasmus Lerdorf In-Reply-To: <488918E3.90705@lerdorf.com> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v926) Date: Fri, 25 Jul 2008 01:19:51 +0100 References: <488918E3.90705@lerdorf.com> X-Mailer: Apple Mail (2.926) X-Spam-Score: -4.0 X-Spam_Report: Spam detection software, running on the system "lovelace.midden.org.uk", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: I spoke to helly about this just there. I'm more than willing to help. We converted a test repository while developing the re2c stuff. Scott On 25 Jul 2008, at 01:05, Rasmus Lerdorf wrote: > Now that Subversion 1.5 has been out for a little while and it is at > the point where it might actually have some benefit to us, do we > have some volunteers who have some time to try converting over the > repository and all the post-commit and ACL rules from CVSROOT? > > Talking to people here at OSCON, the consensus seems to be that > moving to Subversion at this point would worthwhile. The Git/Bzr/ > Merc folks have better tools to deal with a central svn repository > than cvs at this point, and the svn workflow and Windows tools won't > leave all our less technical committers floundering. > > I think the most convenient approach would be to do the conversion > directly on the cvs.php.net machine and run the two side-by-side > with periodic imports to svn while we test things and then a freeze > and a switchover at some point. > > -Rasmus > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > [...] Content analysis details: (-4.0 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.8 ALL_TRUSTED Passed through trusted hosts only via SMTP -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] 0.4 AWL AWL: From: address is in the auto white-list Subject: Re: [PHP-DEV] Volunteers for Subversion 1.5 conversion of cvs.php.net? From: scott@macvicar.net (Scott MacVicar) I spoke to helly about this just there. I'm more than willing to help. We converted a test repository while developing the re2c stuff. Scott On 25 Jul 2008, at 01:05, Rasmus Lerdorf wrote: > Now that Subversion 1.5 has been out for a little while and it is at > the point where it might actually have some benefit to us, do we > have some volunteers who have some time to try converting over the > repository and all the post-commit and ACL rules from CVSROOT? > > Talking to people here at OSCON, the consensus seems to be that > moving to Subversion at this point would worthwhile. The Git/Bzr/ > Merc folks have better tools to deal with a central svn repository > than cvs at this point, and the svn workflow and Windows tools won't > leave all our less technical committers floundering. > > I think the most convenient approach would be to do the conversion > directly on the cvs.php.net machine and run the two side-by-side > with periodic imports to svn while we test things and then a freeze > and a switchover at some point. > > -Rasmus > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php >