Re: [SVN-MIGRATION] Github
| From: | Travis Swicegood | Date: | Wed, 25 Feb 2009 16:51:47 +0000 |
| Subject: | Re: [SVN-MIGRATION] Github | ||
| References: | 1 2 3 4 5 6 7 8 | Groups: | svn.migration |
| Request: | Send a blank email to svn-migration+get-268@lists.php.net to get a copy of this message | ||
On Feb 25, 2009, at 1:38 AM, shire wrote:
- It's got a significantly higher learning curve than something like SVN - It's easier to change history, or to fowl things up with some of the more advanced commands. - I consider it to be a "power" users type tool, you can do a lot of more advanced things but these come with a complexity cost. Unlike SVN which is pretty simple. - I think tools still need some work, specifically web interfaces. - It's pretty easy to import code from SVN and back using git, do we want to move to SVN first (considering we're ready/planning to do so) which will allow more developers to use GIT more?Watch out! Linus is gonna get ya: http://www.linux-mips.org/wiki/Git :-) From my personal experience, the only thing that has historically made Git harder to use is its lack of GUI tools. I imagine if we took a poll of contributors on internals@ very few (if any) use a GUI tool (outside of possibly an IDE) to commit to PHP. You are correct that Git exposes a lot of advanced functionality that can really bite you if you're not careful/don't know what you're doing. That said, you have to be determined to mess up more than your own repository. There's only a handful of commands you really need to know in order to use Git successfully as a contributor to a project. If we move php-src to Git (via GitHub or something else), I'll put my name in the hat to create a Contributing to PHP doc explaining those commands and getting people up to speed. -T