Re: [RFC] Choosing a distributed version control system for PHP (or not). Call for Participation.
| From: | Stas Malyshev | Date: | Fri, 12 Aug 2011 22:57:35 +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 9 10 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-54559@lists.php.net to get a copy of this message | ||
Hi!
On 8/12/11 3:01 PM, Lester Caine wrote:
I think they're describing local modifications for the Drupal site there, not developing Drupal. Think about it: suppose we have Drupal versions 7.0, 7.1, 7.2. Those will be branches. But if you want to do something into each of them, it won't do for each developer to create a private branch for each of them - the amount of branches will quickly get out of control. That's when you'd need forks. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227Branches 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.That is not how Drupal seems to be using git ... http://drupal.org/node/803746#clone - See 'Creating a Working Branch'