Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:47284 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 19950 invoked from network); 15 Mar 2010 02:26:10 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 15 Mar 2010 02:26:10 -0000 Authentication-Results: pb1.pair.com header.from=mozo@mozo.jp; sender-id=permerror Authentication-Results: pb1.pair.com smtp.mail=mozo@mozo.jp; spf=permerror; sender-id=permerror Received-SPF: error (pb1.pair.com: domain mozo.jp from 209.85.221.191 cause and error) X-PHP-List-Original-Sender: mozo@mozo.jp X-Host-Fingerprint: 209.85.221.191 mail-qy0-f191.google.com Received: from [209.85.221.191] ([209.85.221.191:53749] helo=mail-qy0-f191.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id B5/CA-07348-0CA9D9B4 for ; Sun, 14 Mar 2010 21:26:09 -0500 Received: by qyk29 with SMTP id 29so1095360qyk.15 for ; Sun, 14 Mar 2010 19:26:06 -0700 (PDT) MIME-Version: 1.0 Received: by 10.224.72.228 with SMTP id n36mr730077qaj.138.1268619966228; Sun, 14 Mar 2010 19:26:06 -0700 (PDT) In-Reply-To: References: <36D0BC9D-72BA-4087-9088-A054F0E82A52@pooteeweet.org> Date: Mon, 15 Mar 2010 11:25:46 +0900 Message-ID: To: Herman Radtke Cc: Lukas Kahwe Smith , internals@lists.php.net Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] Re: moving forward From: mozo@mozo.jp (Moriyoshi Koizumi) On Mon, Mar 15, 2010 at 6:25 AM, Herman Radtke wro= te: >> Oh no .. another dangerous topic. Again we have been there even before t= he switch. The idea is to keep the centralized repo on svn, because the mas= ses know how it works, the tools are widely available and we have plenty of= experience among us in how to keep svn running. I see little incentive to = move the _central_ repo to a DVCS. Are the bridges to git, mercurial, bzaar= etc really so bad that this topic is worth discussing (no sarcasm, honest = question)? > > I only have experience with git. =A0The problem with something like > git-svn is that your git branch becomes an island. =A0I can't share that > branch with anyone else. =A0So all I really get is git syntax within an > svn environment. There are a number of ways to share your branches with others. At least you can do it by pushing your local changesets to some remote repository. I've actually been experimenting with modified PHP core with some language features added by forking the mirror on github.com [1]. I've never felt any inconvenience there. I really appreciate those who set up the mirror. > I have no problem working with svn and actually prefer it for projects > that use a compiler. =A0For PHP apps, git is great because nothing has > to be built. =A0Bouncing between git branches means I have to recompile > PHP every time (or set up some system of symlinks). I guess you can have several local repositories that have different branches checked out at the same time... [1] http://github.com/moriyoshi/php-src/ Moriyoshi