Using Git for Drupal development discussion

A gig and a half is all of core and contrib.

Drupal core with all of its history is 23 megabytes in a git repository.

Sticky write permissions forces new directories
chmod g+ws -r files

I show people the contents of this directory where I have index.php1, index.php2, index.php3, and why this [is a pain].

Before we even get into the benefits of collaboration.

P not moving toward git until Drupal.org moves toward a DVCS

That's why I have the system with a git copy

It will not be trivial.

Subversion has the best developed tools for the kind of work we deal with it.

Git and Bzr are getting there

Unless git offers us some substantive advantage,

My whole company switched over-- all the developers claimed-- development was just easier with git, hunk-based commit capability. I could just do a lot, and still have sensible task-based

Committing a lot before making it public.

Rebasing. Sam: I get a tingly feeling, the code figuring everything out and putting it into place.

Sensible merging.

Squash, five commits later.

Resolution