On 30/04/10 03:12, Andrew Berry wrote:
On a related topic, anyone using git in a way like how subversion does vendor branches? Currently I do a cvs export => svn with svn_load_dirs.pl, and I'd be really interested on any resources on how to best do this with core and contrib code.
Where I can get a good git checkout [1] of the module I'm using submodules [2] for them all. This allows the superproject just to have info about where (what version) in the module it is. If I need to edit, patch, etc. the module for what ever reason I'm cloning it on a git repo I can write to and just moving the submodule to point there. Then creating actual branches (rather than a headless checkout - see [2] for explanations of the wierd terminology) that I can then commit to my repo for just that module. I'm actually even doing this for core, as a submodule of my superproject. It makes it easy to keep a single copy with patches (simpletest, the extra cron for drupal_queue etc.) and then switch them on the project. I'm guessing I could even add another tracking branch on pressflow - but I've not gone there yet. Cheers, ekes [1] I've stumbled for several modules as the tags don't seem to line up for CVS -> git conversions, so this isn't perfect till everything is moved to git http://github.com/sdboyer/drupal-git-scripts/issues/closed#issue/3 [2] http://book.git-scm.com/5_submodules.html