Re: [RFC] Choosing a distributed version control system for PHP (or not). Call for Participation.
| From: | Stas Malyshev | Date: | Fri, 12 Aug 2011 19:02:14 +0000 |
| Subject: | Re: [RFC] Choosing a distributed version control system for PHP (or not). Call for Participation. | ||
| References: | 1 2 3 4 5 6 7 8 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-54553@lists.php.net to get a copy of this message | ||
Hi!
On 8/12/11 11:47 AM, Lester Caine wrote:
No, no. Pull requests and push/pull are very different things. Having people just push whatever they like whenever they like into main code is what we have now, and it's not really the best way to work on a big project. Please see on github how pull requests are implemented.Pull requests, for one.Push/Pull from local copy?
The TEAM has a master copy on github or better still git.php.net, but you don't need 10000 other copies on github as well? I don't like the code Drupal produce,It's not copies. And yes, I need them - because not every change should immediately go into master repo. Much better way is to publish it in your local repo and have it reviewed and then merged into master repo. Or not. Or merged later. github allows to manage this process better than storing assorted patches in emails and bugs and pastebin, etc.
Sandboxes and development branches are the right way to go, but could actuallyBranches are different things than github forks, for different purposes. Branch is a project, fork is a workspace. You can have multiple people work on a project, using multiple workspaces. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227