On 2011-08-07, Stas Malyshev <smalys...@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).
> > > Please note that it's not "hg vs git" argument as I know very little > about hg and have no experience working with it, but I've read what > people write about it and I'm sure many of git's strengths are present > in hg too. I hope somebody with experience in hg (or both, even better) > will voice in. yes hg offers most of this too. your arguments are general arguments in favor of DVCS. There are some minor differences in branching and file handling so some people call hg easier to learn when coming from SVN. Particularly branching is different in hg as outlined in the RFC, making pure lightweight branches a little bit more difficult to handle than in git, but allowing non-lightweight branches which don't exist in Git (this mean that you can forever tell on which branch a changeset was comitted) -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
