Stas Malyshev wrote:
Branches 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'
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.
Actually they are talking about developing Drupal ... "Once you have finished
working on your fix or feature, you’ll need to bring those changes from your
topic branch back into the main fooproject branch."
Bare in mind that this is more like PEAR code than compiled C code, so the end
target is different but the process is what matters. I'm not sure that is the
right way to be doing this process, but if it's what is documented?
As Herman says ... "Moving svn to a dvcs is less of a technical change and more
of a paradigm shift in the fundamental way a user interacts with version control."
There are many ways that DVCS can be abused, so managing things in an agreed
manner is more what needs to be agreed than the simple - switch to DVCS?
--
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk//
Firebird - http://www.firebirdsql.org/index.php
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
