In terms of svn-like vendor branches, there are many tricks around the web, but the most intelligent discussion I have found is in Chapter 6 of Pro Git, in the discussion of submodules, superproject (a small pithy paragraph which I think touches on the Drupal case) and subtrees.<div>
<br></div><div>It remains to be seen what will emerge as the "Drupal way" here...</div><div><br></div><div>Victor Kane<br><br><div class="gmail_quote">On Thu, Apr 29, 2010 at 10:27 PM, Antonio P. P. Almeida <span dir="ltr"><<a href="mailto:perusio@gmail.com">perusio@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div><div></div><div class="h5">On 30 Abr 2010 02h12 WEST, <a href="mailto:andrewberry@sentex.net">andrewberry@sentex.net</a> wrote:<br>
<br>
> On 2010-04-29, at 5:34 PM, Domenic Santangelo wrote:<br>
><br>
>> With d.o moving to git, I'm becoming more interested in how it<br>
>> works.<br>
><br>
> On a related topic, anyone using git in a way like how subversion<br>
> does vendor branches? Currently I do a cvs export => svn with<br>
> <a href="http://svn_load_dirs.pl" target="_blank">svn_load_dirs.pl</a>, and I'd be really interested on any resources on<br>
> how to best do this with core and contrib code.<br>
<br>
</div></div>Well I'm pretty much ignorant in SVN terminology but in Git, a branch<br>
is just a pointer to a given commit. So you can branch as much as you<br>
want.<br>
<br>
git checkout -b my_new_branch [old_branch]<br>
<br>
Now you're on my_new_branch that was created from old_branch. Work on<br>
it. The old_branch default is HEAD.<br>
<br>
git checkout old_branch<br>
<br>
You're back on old_branch. That's it.<br>
<br>
Git always copies all files that change in a given commit. It doesn't<br>
keep deltas like others SCMs.<br>
<font color="#888888"><br>
--- appa<br>
<br>
</font></blockquote></div><br></div>