Re: [RFC PATCH] clone: add clone.recursesubmodules config option

On Wed, Aug 2, 2017 at 11:11 AM, Jeremy Morton wrote: > Did this ever get anywhere? If not why not? It would be very useful to me > to be able to clone recursively by default, especially considering you can't > use 'alias' to override the existing 'clone' command. > Note

Re: [RFC PATCH] clone: add clone.recursesubmodules config option

Did this ever get anywhere? If not why not? It would be very useful to me to be able to clone recursively by default, especially considering you can't use 'alias' to override the existing 'clone' command. -- Best regards, Jeremy Morton (Jez) On 06/06/2014 06:26, Heiko Voigt wrote: On Thu,

Re: [RFC PATCH] clone: add clone.recursesubmodules config option

On Mon, Oct 03, 2016 at 10:18:32AM -0700, Stefan Beller wrote: > On Mon, Oct 3, 2016 at 8:36 AM, Jeremy Morton wrote: > > Did this ever get anywhere? Can we recursively update submodules with "git > > pull" in the supermodule now? > > I think the idea is sound. I am

Re: [RFC PATCH] clone: add clone.recursesubmodules config option

On Mon, Oct 3, 2016 at 8:36 AM, Jeremy Morton wrote: > Did this ever get anywhere? Can we recursively update submodules with "git > pull" in the supermodule now? I think the idea is sound. >> diff --git a/t/t7407-submodule-foreach.sh b/t/t7407-submodule-foreach.sh >>

Re: [RFC PATCH] clone: add clone.recursesubmodules config option

Did this ever get anywhere? Can we recursively update submodules with "git pull" in the supermodule now? -- Best regards, Jeremy Morton (Jez) On 04/06/2014 10:30, Chris Packham wrote: Add a config option that will cause clone to recurse into submodules as if the --recurse-submodules option

Re: [RFC PATCH] clone: add clone.recursesubmodules config option

Am 06.06.2014 07:54, schrieb Heiko Voigt: On Thu, Jun 05, 2014 at 07:48:33PM +1200, Chris Packham wrote: On 05/06/14 07:42, Heiko Voigt wrote: So either we do this magically and all valid boolean values are forbidden as tags or we would need a different config option. Further thinking about

Re: [git] Re: [RFC PATCH] clone: add clone.recursesubmodules config option

On Mon, Jun 09, 2014 at 03:17:07PM +0200, Jens Lehmann wrote: And by the way: wouldn't it make more sense to tell the user /what/ we do automatically? So maybe 'submodule.autoupdate' is a better name for the new switch? Or autocheckout? No need to preserve submodule-specific jargon when we

Re: [RFC PATCH] clone: add clone.recursesubmodules config option

Heiko Voigt hvo...@hvoigt.net writes: On Thu, Jun 05, 2014 at 07:48:33PM +1200, Chris Packham wrote: ... I'm a little confused at how autoclone and autoinit differ. Aren't they the same? i.e. when this module appears grab it by default. I see autoupdate as a little different meaning update

Re: [RFC PATCH] clone: add clone.recursesubmodules config option

On 05/06/14 07:42, Heiko Voigt wrote: On Wed, Jun 04, 2014 at 10:24:06AM -0700, Junio C Hamano wrote: Chris Packham judge.pack...@gmail.com writes: On 04/06/14 09:05, Junio C Hamano wrote: Also, going --recursive when the user did not want is a lot more expensive mistake to fix than not

Re: [RFC PATCH] clone: add clone.recursesubmodules config option

Jens Lehmann jens.lehm...@web.de writes: ... I believe we should have one or two switches telling Git I want my submodules be updated without having to use the 'git submodule' command. And after that submodule specific overrides can kick in, e.g. when submodule.name.update is set to none the

Re: [git] Re: [RFC PATCH] clone: add clone.recursesubmodules config option

On Thu, Jun 05, 2014 at 11:18:28AM -0700, Junio C Hamano wrote: Jens Lehmann jens.lehm...@web.de writes: We had two settings in mind,... So what if clone would just do an git submodule init for now when submodule.autoinit is set but submodule.autoupdate isn't [?] ... and a single

Re: Re: [RFC PATCH] clone: add clone.recursesubmodules config option

On Thu, Jun 05, 2014 at 11:18:28AM -0700, Junio C Hamano wrote: Jens Lehmann jens.lehm...@web.de writes: We had two settings in mind,... So what if clone would just do an git submodule init for now when submodule.autoinit is set but submodule.autoupdate isn't [?] ... and a single

Re: Re: [RFC PATCH] clone: add clone.recursesubmodules config option

On Thu, Jun 05, 2014 at 07:48:33PM +1200, Chris Packham wrote: On 05/06/14 07:42, Heiko Voigt wrote: I like this idea of specifying different views by giving tags. But does it rule out a boolean clone.recursesubmodules? For the simple case some people might not want to worry about

Re: [RFC PATCH] clone: add clone.recursesubmodules config option

Chris Packham judge.pack...@gmail.com writes: On 04/06/14 09:05, Junio C Hamano wrote: Also, going --recursive when the user did not want is a lot more expensive mistake to fix than not being --recursive when the user wanted to. Having said all that, I do not mean to say that I am opposed

Re: [RFC PATCH] clone: add clone.recursesubmodules config option

Am 04.06.2014 19:24, schrieb Junio C Hamano: Chris Packham judge.pack...@gmail.com writes: On 04/06/14 09:05, Junio C Hamano wrote: Also, going --recursive when the user did not want is a lot more expensive mistake to fix than not being --recursive when the user wanted to. Having said all

Re: Re: [RFC PATCH] clone: add clone.recursesubmodules config option

On Wed, Jun 04, 2014 at 10:24:06AM -0700, Junio C Hamano wrote: Chris Packham judge.pack...@gmail.com writes: On 04/06/14 09:05, Junio C Hamano wrote: Also, going --recursive when the user did not want is a lot more expensive mistake to fix than not being --recursive when the user