A subtree merge doesnt behave like that - it will merge the Zend\Log component into the Symfony2 repository as if it belongs there, but will still have the appropriate history to be able to merge new changes from the ZF framework as they happen.
I dont fully understand how it all works internally, but the subtree merge solution is absolutely acceptable in my opinion until Matt can come up with better packaging solutions for independent components. t On Sat, Dec 4, 2010 at 09:48, Lukas Kahwe Smith <[email protected]> wrote: > > On 03.12.2010, at 22:43, Tim Nagel <[email protected]> wrote: > > > A subtree merge would work in this instance, I am already doing this with > old internal projects that we are migrating to git that are not compatible > with namespace autoloaders like S2's. > > unfortunately i am still struggeling to grok git. but it was my impression > that i still need to download the entire git repo in order to get this > single branch. > > regards > Lukas > > -- > If you want to report a vulnerability issue on symfony, please send it to > security at symfony-project.com > > You received this message because you are subscribed to the Google > Groups "symfony developers" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected]<symfony-devs%[email protected]> > For more options, visit this group at > http://groups.google.com/group/symfony-devs?hl=en > -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
