You can use http://github.com/vjousse/symfony-1.3---1.4 instead of http://github.com/vjousse/symfony-1.4 to stick with specific symfony version between 1.3 & 1.4 branches
With regard, everzet. On Wed, Jun 23, 2010 at 17:09, ryan weaver <[email protected]> wrote: > I haven't tried that specifically - does it work? > > As an aside, there are some versioning problems - I believe that either the > --recursive on "init" or the --recursive on "update" was only added in a > somewhat recent version. Still, that's a diminishing concern. > > Ryan Weaver > Lead Programmer Iostudio, LLC > http://www.sympalphp.org > http://www.thatsquality.com > Twitter: @weaverryan > > > On Wed, Jun 23, 2010 at 8:43 AM, Tom Boutell <[email protected]> wrote: > >> Why is that not ideal? Just want to understand the gotchas >> >> On Wed, Jun 23, 2010 at 1:14 AM, Jeremy Mikola <[email protected]> wrote: >> > On Jun 20, 11:55 am, ryan weaver <[email protected]> wrote: >> >> The git submodule --recursive does work, but you also need to call "git >> >> submodule init" for the first time before that. The problem there is if >> you >> >> have one submodule (which has a nested submodule), your project won't >> be >> >> aware of the embedded submodule until you actually init and update the >> first >> >> submodule. >> > >> > Not ideal, but I believe you could use: git submodule update --init -- >> > recursive >> > >> > -- >> > 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 >> > >> >> >> >> -- >> Tom Boutell >> P'unk Avenue >> 215 755 1330 >> punkave.com >> window.punkave.com >> >> -- >> 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]<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
