Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:54440
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain m.gmane.org designates 80.91.229.12 as permitted sender)
Mail-Followup-To: internals@lists.php.net
Reply-To: internals@lists.php.net
To: internals@lists.php.net
Date: Sun, 07 Aug 2011 23:37:53 +0200
Organization: aich tea tea pea dicky riley dot net
Lines: 47
Message-ID: <ek8vr4hphq.fsf@news.eternal-september.org>
References: <slrnj3tulc.6vi.dsp@experimentalworks.net>
	<4E3F0279.3070701@sugarcrm.com>
	<slrnj3u12r.6vi.dsp@experimentalworks.net>
Mime-Version: 1.0
Content-Type: text/plain
Mail-Copies-To: never
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux)
Cancel-Lock: sha1:YX6XjiDhuJterOswJEAaOD6AWQo=
Subject: Re: [PHP-DEV] [RFC] Choosing a distributed version control system for PHP (or not). Call for Participation.
From: rileyrg@googlemail.com (Richard Riley)

David Soria Parra <dsp@php.net> writes:

> On 2011-08-07, Stas Malyshev <smalyshev@sugarcrm.com> wrote:
>> Hi!
>>
>> As somebody that have seen reasonably big project switch from SVN to git 
>> and worked quite actively with git since then, I think describing my 
>> experience might be useful for those that never tried it.
>>
>> 1. git is much better than svn especially as applied to complex projects 
>> with multiple participants which need to accept outside patches, 
>> maintain multiple branches and port fixes between branches. You never 
>> know how much you needed cheap branching/merging until you worked with 
>> it some.
>>
>> 2. Switching from svn to git requires one to undergo some mental shift, 
>> and for the first couple of weeks you may be confused and somewhat 
>> frustrated by too many things that look like but not exactly like the 
>> old system. It would appear too complex and unnecessarily complicating 
>> workflows. However, as you develop new routines, you'll find out how it 
>> makes sense and will become more effective than with svn. Note that git 
>> IS much more complex conceptually than SVN and allows to do much more 
>> crazy things - including rewriting history in all kinds of weird ways - 
>> so while I don't think I had to ask SVN question in forums for years - I 
>> still have to google "how to do this in git" and ask around for some of 
>> the more complex things. I think it's still worth it. Don't know if it 
>> makes me a fanboy :)
>>
>> 3. Having system like github around it adds a lot - maintaining multiple 
>> repositories, forks and pull requests is a real boon. I'm not sure if it 
>> would make sense for php, all things considered, but there are very 
>> significant benefits of using such a system where many workflows are 
>> already built-in.
> having a dvcs will enable us to use pull requests in github. (maybe
> you will not able to use the big merge button but rather do it yourself,
> but still it's a huge improvement).


Its really simple.

Use git.

It works, is fast and is rapidly becoming the industry standard. Do not
sue something for "moral grounds" like the awful bzr used for emacs.

Its designed as a fast, efficient DVCS.